Legacy Platform
Modernization
AI-first migration of a .NET monolith serving 40,000 users into .NET 8 microservices — 5 engineers, 9 months, zero downtime.
System Architecture
Strangler Fig pattern — incremental migration via YARP gateway
Migration Timeline
4 phases over 9 months — Phase 0 invests in AI foundation
Services
5 services to extract + Payment (frozen in monolith)
Travel Booking
M3Handles all travel booking operations including itineraries, supplier integrations, and pricing. The highest-value core domain with the most complex business rules.
Event Management
M4Manages events, venues, schedules, and attendees. Complex scheduling logic with venue capacity constraints and multi-day event support.
Workforce + Allocation
M6Manages staff profiles, skills, shift allocations, and availability. Subscribes to Travel and Event domain events to coordinate staffing needs.
Communications
M7Cross-cutting notification service handling email, SMS, and push notifications. Subscribes to ALL domain events across the system to trigger appropriate communications.
Reporting (CQRS)
M7Read-only reporting service using CQRS pattern. Aggregates data from all services via CDC and event projections to build cross-module dashboards and reports.
Payment (Legacy)
FrozenPayment 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.