Skip to content

15.1 Containerization

Sprint: Sprint 15 - Deployment
Feature ID: 15.1
Subtasks: 15.1.1, 15.1.2

Objective

Deliver "Containerization" within Sprint 15 - Deployment.

Dependencies

Aggregated from the subtasks below (prerequisite task IDs and enablers):

  • Sprints 04-12
  • 15.1.1
  • 1.4.1

Subtasks

15.1.1 Production Dockerfiles for all services

  • ID: 15.1.1
  • Title: Finalize multi-stage Dockerfiles for every service
  • Description: Ensure each of the 13 services (3 infra + 10 domain) has a multi-stage, layered, non-root, JRE-21 image with a healthcheck and the actuator health endpoint exposed.
  • Business Purpose: Reproducible, secure runtime artifacts (ADR-014).
  • Inputs: ADR-014, analysis Section 11.
  • Outputs: Dockerfiles per service.
  • Acceptance Criteria:
  • Each image builds, runs as non-root, starts, and reports healthy via its actuator probe.
  • Dependencies: Sprints 04-12
  • Complexity: M

15.1.2 Image build and registry push in CI

  • ID: 15.1.2
  • Title: Build and push images on merge
  • Description: CI stage building each changed service image, tagging by version+commit, and pushing to the container registry (ADR-014).
  • Business Purpose: Continuous delivery of deployable artifacts (ADR-014).
  • Inputs: ADR-014, 1.4.1.
  • Outputs: CI image build/push stage.
  • Acceptance Criteria:
  • A merge produces versioned images in the registry for changed services.
  • Dependencies: 15.1.1, 1.4.1
  • Complexity: M

Acceptance Criteria

Each subtask above carries its own objective, testable acceptance criteria. This feature is complete when every subtask's acceptance criteria are met.

Deliverables

  • Dockerfiles per service.
  • CI image build/push stage.

Definition of Done

  • All subtasks (15.1.1, 15.1.2) completed and their acceptance criteria verified.
  • All listed dependencies satisfied.
  • Build and tests green per the global conventions in ../README.md (Section 3).