0x1d
38a251968c
Transform all documentation from modular monolith to true microservices
architecture where core services are independently deployable.
Key Changes:
- Core Kernel: Infrastructure only (no business logic)
- Core Services: Auth, Identity, Authz, Audit as separate microservices
- Each service has own entry point (cmd/{service}/)
- Each service has own gRPC server and database schema
- Services register with Consul for service discovery
- API Gateway: Moved from Epic 8 to Epic 1 as core infrastructure
- Single entry point for all external traffic
- Handles routing, JWT validation, rate limiting, CORS
- Service Discovery: Consul as primary mechanism (ADR-0033)
- Database Pattern: Per-service connections with schema isolation
Documentation Updates:
- Updated all 9 architecture documents
- Updated 4 ADRs and created 2 new ADRs (API Gateway, Service Discovery)
- Rewrote Epic 1: Core Kernel & Infrastructure (infrastructure only)
- Rewrote Epic 2: Core Services (Auth, Identity, Authz, Audit as services)
- Updated Epic 3-8 stories for service architecture
- Updated plan.md, playbook.md, requirements.md, index.md
- Updated all epic READMEs and story files
New ADRs:
- ADR-0032: API Gateway Strategy
- ADR-0033: Service Discovery Implementation (Consul)
New Stories:
- Epic 1.7: Service Client Interfaces
- Epic 1.8: API Gateway Implementation
39 lines
1.5 KiB
Markdown
39 lines
1.5 KiB
Markdown
# Story 3.5: Service Registry and Discovery (Verification)
|
|
|
|
## Metadata
|
|
- **Story ID**: 3.5
|
|
- **Title**: Service Registry and Discovery (Verification)
|
|
- **Epic**: 3 - Module Framework (Feature Services)
|
|
- **Status**: Pending
|
|
- **Priority**: High
|
|
- **Estimated Time**: 2-3 hours
|
|
- **Dependencies**: 1.7, 3.1
|
|
|
|
## Goal
|
|
Verify and document integration of Consul service registry (implemented in Epic 1) with feature services. Ensure all services can register and discover each other correctly.
|
|
|
|
## Description
|
|
This story verifies that the Consul service registry implemented in Epic 1 (Story 1.7) works correctly with feature services. It ensures service registration, discovery, and health checking work for both core services and feature services.
|
|
|
|
## Deliverables
|
|
|
|
### 1. Service Registry Verification
|
|
- Verify Consul registry implementation from Epic 1 works correctly
|
|
- Test service registration for feature services
|
|
- Test service discovery for feature services
|
|
- Verify health checking integration
|
|
|
|
### 2. Integration Documentation
|
|
- Document how feature services register with Consul
|
|
- Document service discovery patterns for feature services
|
|
- Update examples to show feature service registration
|
|
|
|
### 3. Integration Tests
|
|
- Test feature service registration
|
|
- Test feature service discovery
|
|
- Test health checking for feature services
|
|
- Test service client integration with Consul
|
|
|
|
**Note:** Service registry implementation is in Epic 1 (Story 1.7). This story verifies integration with feature services.
|
|
|