Building a Distributed Datastore in 8 Weeks
summary
Four students build a working distributed datastore in eight weeks: a REST API (Spring Boot, H2, Postman) with a hub coordinator with DB that registers nodes, propagates membership, and performs leader election; shards by bookstore so there is one server per bookstore; clients see API-only endpoints and face 301 redirects or server-forwards for reads and writes; leader-based batch writes use health checks, re-election, retries, circuit-breakers (resilience4j), fallbacks, rate limiting, ngrok for testing, and request-id correlated logging.
AI-written summary · about
chapters (7)
- 0:00Start
- 6:33Structure
- 12:36Possible Issues at Scale
- 14:21Possible Solutions
- 39:14Wrap up
- 48:31What Did I Learn?
- 51:32Critical Feedback
related talks
45mDo Distributed Systems they said. It'll be fun they said.
21mBuilding Distributed Platforms at Extreme Scale on Fast Changing Data
41mDistributed Systems explained with NodeJS
30mA tale of two distributed systems through the lens of a developer
41mIntroduction to distributed systems
01h 23mBuilding Highly-Scalable Spring Applications with In-Memory, Distributed Data Grids
01h 08mDistributed Java Databases Under the Hood
25mGrowing Distributed Systems