Cloud Native Database Meetup Japan: The State of Distributed Database in Japan
summary
Companies in Japan are moving from single-node RDBs to distributed SQL like YugabyteDB to solve write bottlenecks, availability and geo distribution. Examples: an e‑commerce team replaces Aurora to gain automatic shard rebalancing and elastic node counts for campaign-driven peaks; Rakuten Mobile runs 1.5 petabytes across ~300 nodes replicated across three data centers; a mobile game uses Google Cloud Spanner as a managed alternative. Key techs are Raft-based replication, sharding, multi‑region multi‑primary setups and distributed transactions with HLCs.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:06Relational DB challenges
- 3:16DB system complexity
- 6:25Distributed SQL benefits
- 7:48Sharding explained
- 9:18Raft for high availability
- 14:02Distributed transactions
- 16:35APNIC case study
- 18:23Rakuten Mobile case
- 19:53Cloud distributed SQL
- 20:58YugabyteDB features
- 22:43YugabyteDB deployment
- 24:38Summary and outlook
related talks
30mBuilding Cloud Native Applications on Distributed SQL Platform
31mLatest Developments / Japan Business and Product Updates
25mScaling Innovation: Rakuten’s Cloud-Native & AI Journey with
24mTech Roundtable: Distributed SQL Around the World
19mBuild Global-Scale Apps Using Globally Distributed Autonomous Databases
29mCloud Native Patterns – Shifting Responsibilities
29mEnterprise Scale: How a Distributed Architecture Can Deliver Scale and Resilience
30mFrom monolith to petabyte scale: Built a cloud-native, AI-ready data layer