How Micro-Service Patterns Change When the Database Scalable

on YouTube ↗27m

" summary

Argues that a globally consistent, scalable database reshapes microservice choices by restoring single-database options and shifting complexity from engineers back into the data tier. Demonstrates Fauna with FQL user-defined functions, temporality and time-based migrations, optimistic concurrency for hot documents, and push-based CDC to Rockset for analytics. Shows composition of functions to isolate team APIs, a counter-sharding pattern to avoid write contention, and notes cross-database transactions are desirable but not yet implemented. Practical demos mostly work; some features remain requests.

AI-written summary · about

" chapters (6)

1. 0:00Intro
2. 0:49Evolution of data
3. 3:48How do patterns change?
4. 8:11Starting of with a monolith
5. 11:05Data choices?
6. 21:14An example

" related talks

• 47mMigrating to Microservice DatabasesEdson Yanaga · Oredev 2017
• 30mDatabases in the Microservices WorldRob Richardson · Berlin Buzzwords 2021
• 01h 05mMigrating to Microservice Databases: From Relational Monolith to Distributed DataEdson Yanaga · NDC Porto 2019
• 58mDatabases in the Microservices WorldRob Richardson · Developers Summit 2021
• 54m3 Patterns for Scalable MicroservicesThorben Janssen · JCON-ONLINE 2021
• 31mHarness the Power of a Single Database for MicroservicesFranck Pachot · Infobip Shift 2023
• 51mData management in a Microservices worldGerald Venzl · JCON 2020
• 47mHow to Choose a Right Database for Your Microservices?Vamsi Mohan Vandrangi · Open Source Summit + Embedded Linux Conference + OSPOCon 2021