Data in a Microservices world from conundrum to options
summary
Shows how to move from a monolithic DB to microservices using a virtual database that speaks JDBC/ODBC, exposes read‑write domain views with field mapping and anonymization, and lets teams migrate gradually and roll back without changing the legacy DB. Demonstrates a hotel booking demo on OpenShift where killing pods and routing 75% traffic to v2 still preserves in‑progress bookings because state lives in an Infinispan data grid with cross‑DC replication. Recommends event streams via Debezium + Kafka for CDC and real‑time consumers.
AI-written summary · about
chapters (15)
- 0:00Start
- 1:02MSA has many benefits
- 2:33Monolith to microservices
- 4:10Big bang approach
- 8:44Evolving microservices schemas
- 13:37Challenge: New functionality requirements with tight deadlines
- 14:29Demo Architecture: Functional
- 14:47The Monolith Application
- 15:17Breaking up the monolithic database virtually
- 21:41The challenge of state
- 30:57Microservices data islands
- 33:03Change data capture to the rescue
- 36:03Creating Front-End Applications
- 42:11Benefits demonstrated
- 42:52Summary
related talks
01h 05mMigrating to Microservice Databases: From Relational Monolith to Distributed Data
51mData management in a Microservices world
47mMigrating to Microservice Databases
55mThe hardest part of microservices: Your Data
30mDatabases in the Microservices World
58mDatabases in the Microservices World
12mTen Things I Hate About Microservices
25mData-Driven Migration from Monoliths to Event-Driven Microservices