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
5.1 KiB
5.1 KiB
Complete Task List
This document provides a comprehensive list of all tasks across all epics. Each task has a corresponding detailed file in the epic-specific directories.
Task Organization
Tasks are organized by epic and section. Each task file follows the naming convention: {section}.{subtask}-{description}.md
Epic 0: Project Setup & Foundation
Epic 0 Stories
- 0.1 Project Initialization and Repository Structure
- 0.2 Configuration Management System
- 0.3 Structured Logging System
- 0.4 CI/CD Pipeline and Development Tooling
- 0.5 Dependency Injection and Application Bootstrap
Epic 1: Core Kernel & Infrastructure
- 1.1 Enhanced DI Container - Core kernel services only
- 1.2 Database Client Foundation - Per-service database connections
- 1.3 Health & Metrics System
- 1.4 Error Handling
- 1.5 HTTP/gRPC Server Foundation - Server foundations for services
- 1.6 OpenTelemetry - Distributed tracing across services
- 1.7 Service Client Interfaces - Service client interfaces
- 1.8 API Gateway Implementation - API Gateway as core infrastructure
- Epic 1 Overview
Epic 2: Core Services (Authentication & Authorization)
- 2.1 Auth Service - JWT Authentication - Independent Auth Service
- 2.2 Identity Service - User Management - Independent Identity Service
- 2.3 Authz Service - Authorization & RBAC - Independent Authz Service
- 2.4 Role Management (Part of Authz Service) - Role management gRPC endpoints
- 2.5 Audit Service - Audit Logging - Independent Audit Service
- 2.6 Database Seeding - Per-service seeding
- Epic 2 Overview
Epic 3: Module Framework (Feature Services)
- 3.1 Module System Interface - Module interface for feature services
- 3.2 Permission Code Generation
- 3.3 Service Loader - Service initialization helpers
- 3.4 Service Management CLI - Service management CLI
- 3.5 Service Registry Verification - Verify Consul integration
- Epic 3 Overview
Epic 4: Sample Feature Service (Blog Service)
- 4.1 Complete Blog Service - Blog Service as reference implementation
- Epic 4 Overview
Epic 5: Infrastructure Adapters
- 5.1 Cache System
- 5.2 Event Bus
- 5.3 Blob Storage
- 5.4 Email Notification
- 5.5 Scheduler & Jobs
- 5.6 Secret Store
- 5.7 Advanced gRPC Features - Streaming, gRPC-Gateway (basic gRPC in Epic 1-2)
- Epic 5 Overview
Epic 6: Observability & Production Readiness
- 6.1 Enhanced Observability
- 6.2 Error Reporting
- 6.3 Grafana Dashboards
- 6.4 Rate Limiting
- 6.5 Security Hardening
- 6.6 Performance Optimization
- Epic 6 Overview
Epic 7: Testing, Documentation & CI/CD
Epic 8: Advanced Features & Polish
- 8.1 OIDC Support
- 8.2 GraphQL API
- 8.3 Additional Sample Feature Services - Notification & Analytics Services
- 8.4 Final Polish
- Epic 8 Overview
Note: API Gateway is now in Epic 1 (Story 1.8) as core infrastructure, not an advanced feature.
Task Status Tracking
To track task completion:
- Update the Status field in each task file
- Update checkboxes in the main plan.md
- Reference task IDs in commit messages:
[0.1.1] Initialize Go module - Link GitHub issues to tasks if using issue tracking
Generating Missing Task Files
A script is available to generate task files from plan.md:
cd docs/tasks
python3 generate_tasks.py
Note: Manually review and refine generated task files as needed.