A tale of two distributed systems through the lens of a developer
summary
A full retail e‑commerce stack (product, inventory, notification, config, discovery, gateway) is generated and deployed on Kubernetes without hand‑wiring integrations, using a JHipster extension generator-ybdb and YugabyteDB YSQL as the distributed persistent store. The database uses Raft consensus, shards data across tablet servers and runs with replication factor 3, while scaffold builds Uber‑jars, Docker images and deploys them to the cluster; the demo runs and serves seeded data.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:12Why distributed systems matter
- 2:38Application architecture evolution
- 5:05Monolith vs microservices
- 6:51Traditional data layer challenges
- 8:36Distributed SQL and YugabyteDB
- 12:07Kubernetes and YugabyteDB similarities
- 13:15JHipster apps with YugabyteDB
- 15:09Demo workflow
- 19:50Generating multi-service apps
- 21:18Deploying to Kubernetes
- 25:52Live app demo
- 29:54Q&A
related talks
30mImproving a Developer’s Life with Distributed SQL
31mAn Adventure in Multi Cloud with Kubernetes and Distributed Data
29mKong + Yugabyte: Simplifying App Development in a Distributed World
36mFireside Chat with Kroger: Examining their Two-Year Distributed SQL Journey & What's Next
33mBuilding an Elastic, Resilient Data Layer to Power New Retail Experiences
31mEnd-to-End Stack: Harnessing YugabyteDB & Ecosystem Solutions, Build Apps on Global Scale
26mLeveraging a Distributed SQL Database at Tokopedia: Best Practices & Lessons Learned
48mDistributed EclipseStore Applications and Microservices on Kubernetes