Persistence layers for microservices – the converged database approach
summary
Argues that using a converged database reduces operational sprawl by using Oracle’s built-in JSON type and graph/spatial features (made free Dec 5 2019) instead of standing up MongoDB/Elastic/Postgres for every microservice. Describes an automated CI/CD flow that creates and drops 1200 PDB creations (over 1.5 years, >2000 total) and a multi-tenant rollout that lets teams deploy microservice databases in ~10 minutes; cites a case of 150 DBs upgraded in 4 hours. Mentions Rocket.Chat depended on Mongo and a custom REST API built by DBAs+devs.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker intro
- 10:02Microservices and DevOps shift
- 22:50Challenges with microservices data
- 28:13Single vs multi-model databases
- 33:55JSON and Oracle database features
- 38:57Use cases and Oracle solutions
- 41:05Oracle DB multi-tenant demo
- 48:05Evaluating new database systems
- 54:04Key takeaways and Q&A
related talks
51mData management in a Microservices world
30mDatabases in the Microservices World
44mA Software Engineer's Journey Through Microservices Data Sharing
46mData in a Microservices world from conundrum to options
31mHarness the Power of a Single Database for Microservices
01h 05mMigrating to Microservice Databases: From Relational Monolith to Distributed Data
27mHow Micro-Service Patterns Change When the Database Scalable
40mRethinking Microservice Persistence: Beyond the Database Monolith