Migrating from a monolith to a new service
summary
Stack Overflow extracts the moderator messaging feature into a standalone service with its own database, ships the UI as an embeddable frontend component, and deploys it via a monolith proxy so browsers only talk to the original host while the service stays private — the migration uses JWT auth, a simple static JS bundle, and scheduled imports instead of an outbox, accepts eventual consistency with a ~10‑minute sync, follows the strangler fig pattern, and successfully deploys without downtime.
AI-written summary · about
chapters (9)
- 0:00Monolith migration challenges
- 3:34Finding migration candidate
- 13:42Conway's law and teams
- 17:55Strangler fig pattern
- 23:09UI components in new service
- 33:46Data sync between services
- 42:35Avoiding circular dependencies
- 51:02Eventual consistency trade-offs
- 54:53Pragmatic migration decisions
related talks
01h 01mMigrating from a monolith to a new service
40mMigrating from a monolith to a new service
42mQ&A - Monolith to Microservices
47mFrom Monolith to Microservices With the Strangler Pattern
30mMonolith-ifying perfectly good microservices
48mMicroMonolith
36mMicroservices Lessons Learned
33mFireside chat - Monoliths, Microservices & Modernization – Practical Strategies