Microservices in a Monolith

on YouTube ↗23m

" summary

A legacy PHP monolith of about 3 million LOC and ~500k daily requests is incrementally modularized by introducing event sourcing plus small, decoupled modules. The team implemented a ticket service and a user service that run inside the same deployable but communicate via dispatched events and listeners, keeping creation and purchase logic local, resolving race conditions and locking, and reducing coupling without a full rewrite.

AI-written summary · about

" chapters (7)

1. 0:00Legacy monolith challenges
2. 3:51Monolith codebase structure
3. 7:28Microservices architecture
4. 11:01Isolating user service
5. 14:55Refactoring registration and tickets
6. 18:50Event-driven microservices
7. 21:44Key takeaways

" related talks

• 23mMicroservices within a MonolithJoop Lammerts · DevDays Europe 2019
• 48mMicroservices vs The Distributed MonolithChris Riley · Dutch PHP Conference 2018
• 35mLegacy Monolith to MicroservicesSmit Thakkar · DevConf.CZ 2019
• 08mWhy we are writing a monolith, not a microserviceSupriya Srivatsa · LeadDev London 2022
• 57mModularizing the MonolithJimmy Bogard · NDC Oslo 2024
• 57mSplitting Monolith Application to MicroservicesAndrei Shakirin · ApacheCon@Home 2021
• 47mMicroservices? Monoliths? An Annoying Discussion!Eberhard Wolff · JCON-ONLINE 2021
• 40mBreaking the Monolith! Decoupling a Legacy Monolithic ApplicationRodrigo Orofino · QCon São Paulo 2019