Core Services
Extract the two highest-value core domains — Travel Booking and Event Management — while establishing the Payment ACL bridge to the frozen legacy module.
AI Application in This Phase
What AI Does
AI agent receives legacy module → generates .NET 8 service scaffold → translates business logic → generates contract tests → creates PR. Human reviews and adjusts. ~70% of migration code AI-generated.
Expected Impact
30-40% faster per service extraction. AI reuses patterns: Event extraction 25% faster than Travel because templates are calibrated.
Key Deliverables
Week-by-Week Breakdown
| Period | D1 – Tech Lead | D2 – Sr Backend | D3 – Backend | D4 – Fullstack | D5 – FE/DevOps | Output |
|---|---|---|---|---|---|---|
| M2 W1–2 | YARP Gateway routing + ACL scaffold | Travel API (CRUD endpoints) | Event API scaffold | Workforce domain modeling | IaC environments (Dev, Staging) | Gateway + Travel 30% |
| M2 W3–4 | Payment ACL implementation | Travel business logic migration | Event CRUD implementation | React: Travel module UI | Travel CDC setup | ACL MVP, Travel 60% |
| M3 W1–2 | Travel cutover (5% → 100%) | Travel contract tests + bug fixes | Event business logic migration | React: Travel UI polish | Travel monitoring dashboard | ✅ Travel LIVE |
| M3 W3–4 | Code review + architecture guidance | Event business logic support | Event workflows (create/cancel/modify) | React: Event module UI | Event CDC setup | Event 70% |
| M4 W1–2 | Event cutover (5% → 100%) | Event contract tests + stabilize | Event integration tests | Workforce API implementation | React: Event UI polish | ✅ Event LIVE |
| M4 W3–4 | Workforce architecture review | Payment ACL hardening | Comms service scaffold + analysis | Workforce business logic | React: Workforce module start | ACL production-ready |
Services (3)
Travel Booking
CoreHandles all travel booking operations including itineraries, supplier integrations, and pricing. The highest-value core domain with the most complex business rules.
Event Management
CoreManages events, venues, schedules, and attendees. Complex scheduling logic with venue capacity constraints and multi-day event support.
Payment (Legacy)
Core (Frozen)Payment processing and invoicing — remains in the legacy monolith during Phase 1 due to the constraint. New services access it via an Anti-Corruption Layer (ACL) adapter pattern.
Exit Criteria / Go-No-Go Gate
Milestones (3)
Risk Notes
Travel Booking has highest extraction complexity. 2 weeks buffer built in. If Travel takes longer → defer Event start by 2 weeks max, D1 pair-programs with D2. Payment ACL is the critical integration point — must validate early in M2.