Scale Out
Extract the remaining three services — Workforce, Communications (production), and Reporting (CQRS) — completing the full microservices decomposition.
AI Application in This Phase
What AI Does
AI batch-migrates using patterns proven in Phase 1. Template reuse → each service faster. AI generates CQRS read models from existing SQL queries for Reporting. ~75% AI-generated code.
Expected Impact
Save ~3 weeks boilerplate. Reporting CQRS models generated almost entirely by AI from legacy SQL. Comms event handlers generated from specifications.
Key Deliverables
Week-by-Week Breakdown
| Period | D1 – Tech Lead | D2 – Sr Backend | D3 – Backend | D4 – Fullstack | D5 – FE/DevOps | Output |
|---|---|---|---|---|---|---|
| M5 W1–2 | Architecture review + tech debt | Workforce business logic review | Comms API (email/SMS/push) | Workforce business logic + tests | React: Workforce UI | Comms 30%, Workforce 60% |
| M5 W3–4 | Comms architecture + ACL improvements | Comms event triggers | Comms template engine migration | Workforce CDC + cutover prep | Reporting analysis + scaffold | Comms 60%, Workforce 80% |
| M6 W1–2 | Workforce cutover (5% → 100%) | Comms event-driven triggers | Comms integration tests | React: Comms UI | Reporting data aggregation | ✅ Workforce LIVE |
| M6 W3–4 | Reporting CQRS architecture design | Reporting query APIs | Comms CDC + cutover prep | React: Reporting dashboards start | Reporting scheduled jobs | Reporting 50%, Comms 90% |
| M7 W1–2 | Comms cutover (5% → 100%) | Cross-service integration tests | Reporting scheduled reports | React: Reporting dashboards | Production monitoring setup | ✅ Comms LIVE |
| M7 W3–4 | Reporting cutover (5% → 100%) | Performance baseline measurement | Bug fixes across services | React: cross-module integration | Load testing preparation | ✅ Reporting LIVE |
Services (3)
Workforce + Allocation
SupportingManages staff profiles, skills, shift allocations, and availability. Subscribes to Travel and Event domain events to coordinate staffing needs.
Communications
GenericCross-cutting notification service handling email, SMS, and push notifications. Subscribes to ALL domain events across the system to trigger appropriate communications.
Reporting (CQRS)
SupportingRead-only reporting service using CQRS pattern. Aggregates data from all services via CDC and event projections to build cross-module dashboards and reports.
Exit Criteria / Go-No-Go Gate
Milestones (3)
Risk Notes
Phase 2 has the highest parallelism — 3 services in flight simultaneously. Key risk: Comms + Reporting go-live compressed into M7. If Workforce slips → defer Reporting to Phase 3. Scope lever: Reporting is NICE-TO-HAVE if timeline is tight.