Modernising in Healthcare: a case study in decision making
summary
A healthcare monolith with PHP, Delphi and Java is migrated by doing a lift-and-shift then rewrite: EC2 hosts for immediate cloud delivery while a cloud-native rewrite on ECS replaces long-running, customer-specific syncs. EMR connectors hide SOAP/.NET3 and TCP/XML oddities behind a proxy adapter, handling 30k–50k patient syncs that can take 3–4 hours while message syncs run every 3 minutes. Orchestrated scheduled syncs coexist with an event-driven reminder generator; observability uses correlation IDs and structured logs and the result is a cleaner, monitorable system.
AI-written summary · about
chapters (11)
- 0:00Introduction and legacy analogy
- 1:01Context about MJOG application
- 10:56Lift and shift vs cloud rewrite
- 13:54Decomposing complex application
- 19:59EMR service implementation
- 26:02Synchronization service design
- 32:26Orchestration vs choreography
- 34:58Observability in the cloud
- 39:15Defining requirements for legacy
- 41:41Outcome and lessons learned
- 43:26Two years later and final thoughts
related talks
41mAdopting Microservices in Healthcare, Breaking Apart the Monolith
12mHealthcare Access with Data Integration and Microservices
13mBuilding the next-gen healthcare platform using cloud native bingo
58mLegacy modernization made practical: A live coding example of modernization patterns
33mAI assisted legacy modernisation : From UX to code
07mTransforming legacy systems with modern technology demands
26mModernizing VistA, ClearHealth's Invaluable Lessons from 'Legacy' ...
41mModernizing Legacy Apps - Platforms and Strategies