Migrating from a monolith to a new service
summary
Stack Overflow extracts the moderator messaging widget into a new microservice, moving message data to a separate DB and rebuilding the UI as a Svelte embeddable component loaded via an import module. Authentication uses a proxy in the monolith that signs JWTs so the service stays private. Data arrives via an initial import plus periodic pushes (configurable, typically 10 minute eventual consistency), supports ~150 sites, and deploys without downtime.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:17What is a monolith
- 2:59Messaging system
- 4:15Domain driven design
- 7:41Independent service
- 9:59Team resources
- 11:51Team independence
- 13:02Conways law
- 16:27Postits
- 18:35Latest Messages
- 20:18Why the Message Widget
- 23:13The UI
- 24:43Embedding the widget
- 27:11Sequence diagram
- 33:41JSON response
- 35:30Demo
- 36:15Circular reference
- 37:50What about your other host
- 41:45Local development
- 42:52Data
- 47:52Eventually consistency
- 51:18Moving to the new service
- 55:53Wrap up
related talks
57mMigrating from a monolith to a new service
40mMigrating from a monolith to a new service
42mQ&A - Monolith to Microservices
40mBreaking the Monolith! Decoupling a Legacy Monolithic Application
30mMonolith-ifying perfectly good microservices
36mMicroservices Lessons Learned
35mMicroservices: A Tale of 3 Heroes
32mFrom Monolith to Micro Frontend