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
2.0 KiB
2.0 KiB
Implementation Tasks
This directory contains detailed task definitions for each epic of the Go Platform implementation.
Task Organization
Tasks are organized by epic, with each major task section having its own detailed file:
Epic 0: Project Setup & Foundation
- Epic 0 Tasks - All Epic 0 tasks
Epic 1: Core Kernel & Infrastructure
- Epic 1 Tasks - All Epic 1 tasks
Epic 2: Core Services (Authentication & Authorization)
- Epic 2 Tasks - Auth, Identity, Authz, Audit as independent services
Epic 3: Module Framework (Feature Services)
- Epic 3 Tasks - Module framework for feature services
Epic 4: Sample Feature Service (Blog Service)
- Epic 4 Tasks - Blog Service as reference implementation
Epic 5: Infrastructure Adapters
- Epic 5 Tasks - All Epic 5 tasks
Epic 6: Observability & Production Readiness
- Epic 6 Tasks - All Epic 6 tasks
Epic 7: Testing, Documentation & CI/CD
- Epic 7 Tasks - All Epic 7 tasks
Epic 8: Advanced Features & Polish (Optional)
- Epic 8 Tasks - All Epic 8 tasks
Task Status
Each task file includes:
- Task ID: Unique identifier (e.g.,
0.1.1) - Title: Descriptive task name
- Epic: Implementation epic
- Status: Pending | In Progress | Completed | Blocked
- Priority: High | Medium | Low
- Dependencies: Tasks that must complete first
- Description: Detailed requirements
- Acceptance Criteria: How to verify completion
- Implementation Notes: Technical details and references
- Related ADRs: Links to relevant architecture decisions
Task Tracking
Tasks can be tracked using:
- GitHub Issues (linked from tasks)
- Project boards
- Task management tools
- Direct commit messages referencing task IDs
Task Naming Convention
Tasks follow the format: {epic}.{section}.{subtask}
Example: 0.1.1 = Epic 0, Section 1 (Repository Bootstrap), Subtask 1