Cloud Native Spring for Relational Databases
summary
Shows a concrete path from single node Postgres to a distributed SQL deployment using example code that runs with Spring Data R2DBC and a Postgres‑compatible store named Gigabyte (Postgres‑compatible), keeping controllers, repositories and domain objects unchanged. Claims reads scale easily but writes do not, measures and optimizes cost per transaction, and demonstrates that the same Spring abstractions let apps move to a distributed backend with minimal code change using available drivers and sample repos that already work.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:56Use Cases
- 2:59Three Buckets
- 6:33Scaling
- 7:52R2DBC
- 9:03Cost Per Transaction
- 11:04Why Does It Matter
- 11:52What Do We Do
- 14:21Spring Data R2DBC
related talks
26mNewSQL: concepts, realities and when you should embrace it
12mNewSQL Leveraging PostgreSQL
41mCloud-Native Databases in Kubernetes with OpenShift and Postgres
25mCloud Native Data on K8s: The Good, Bad, and the Unknown
14mPlanetary Scale Postgres for Spring Boot Apps: A Fast Migration Path for Devs
26mBeyond the DBaaS Trap: Achieving Data Sovereignty With Kubernetes and CloudnativePG
30mBuilding Cloud Native Applications on Distributed SQL Platform
30mThe database trends that are transforming your database infrastructure forever