A Software Engineer's Journey Through Microservices Data Sharing
summary
A pizza‑platform monolith becomes separate bounded services but keeps a shared DB until coupling, scaling, and migration pain force a switch to database‑per‑service; the team evaluates concrete options: synchronous service‑to‑service REST/gRPC and Apollo Federation for on‑demand aggregation, asynchronous events with Kafka/Confluent schema registry and CDC for decoupling, and background materialization jobs that populate a materialized review service that combines data from four services; for a latency‑sensitive UI they pick materialization, for quick delivery they accept service‑to‑service calls.
AI-written summary · about
chapters (9)
- 0:00Microservices data sharing intro
- 3:21Data sharing techniques
- 6:54Shared database drawbacks and benefits analysis
- 12:16Database per service switch
- 17:52Real-time data with API composition
- 26:48Event-based background integration
- 33:01Data access pattern framework
- 34:06Key takeaways and challenges
- 42:10Q&A on event schemas
related talks
24mPatterns of Evolution from Monolith to Microservices
36mMicroservices Lessons Learned
25mFrom Millions of Customers to Petabytes of Data: A Journey to Microservices
23mLegacy, Open source, microservices and data architecture
51mScaling yout Architecture with Services and Events
44mRoute to microservices the epic voyage of a fintech leader
51mData management in a Microservices world
59mHow to Escape The Distributed Monolith