Moving People with Clojure
summary
Go-Jek rewrites its core Allocation Service from Go into Clojure, matching drivers from a fleet of 100k drivers at over 100k bookings per hour while running on eight machines. The team finishes the rewrite in two months, validates it with two weeks of live-traffic duplication via go-replay and side-by-side matching, uses generative tests (≈100k checks across ~150 suites), Prismatic schema, Hystrix circuit breakers, etcd for hot config, Mount for lifecycle, and ships features 5x faster with a smooth incremental rollout.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:34Prologue
- 3:50Architecture
- 5:05Why Rewrite?
- 8:32Testing the Rewrite
- 10:42Releasing the Rewrite
- 12:43Generative Testing
- 15:02swagger
- 15:31Circuit Breaker
- 16:19Netflix Hystrix
- 16:49Hystrix Dashboard
- 20:41tolitius/mount
- 23:09Either Monad
- 25:23Epilogue
related talks
44mRaising Services and People with Clojure
31mClojure at 4,000 msg/s-What We Learned, Loved, and Loathed
01h 02mSolving Problems the Clojure Way
40mGetting 50,000 Companies on Board with Clojure
42mWhy Clojure?
27mPower to the (Mobile) People: Clojure and GraphQL
41mPredicting Vehicle Usage with Clojure
38m"Growing Data Center networking mgmt UI using ClojureScript, Reagent and re-frame"