Skip to content

4.2 Discovery Server

Sprint: Sprint 04 - Platform Infrastructure Services
Feature ID: 4.2
Subtasks: 4.2.1, 4.2.2

Objective

Deliver "Discovery Server" within Sprint 04 - Platform Infrastructure Services.

Dependencies

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

  • 4.1.1
  • 4.2.1

Subtasks

4.2.1 Discovery-server application

  • ID: 4.2.1
  • Title: Implement Eureka discovery server (8761) for dev
  • Description: Create microservices/discovery-server running Eureka for local/dev service registration and lookup. Document that production uses Kubernetes-native discovery (ADR-010).
  • Business Purpose: Dynamic service location for gateway routing and inter-service calls (dev).
  • Inputs: ADR-010, analysis Section 7.
  • Outputs: discovery-server app, Dockerfile.
  • Acceptance Criteria:
  • The Eureka dashboard is reachable on 8761; a registered sample client appears in the registry.
  • Dependencies: 4.1.1
  • Complexity: S

4.2.2 Service registration defaults in the template

  • ID: 4.2.2
  • Title: Add discovery-client registration to the service template
  • Description: Update the service template and config-server defaults so every domain service registers with discovery in dev (Eureka client) and is discoverable by name.
  • Business Purpose: New services auto-join the registry without per-service wiring.
  • Inputs: 4.2.1, 3.4.1.
  • Outputs: Template + config updates enabling discovery client.
  • Acceptance Criteria:
  • reference-service (or template instance) registers and is listed in Eureka by its service id.
  • Dependencies: 4.2.1
  • Complexity: S

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

  • discovery-server app, Dockerfile.
  • Template + config updates enabling discovery client.

Definition of Done

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