How Nubank leverages Datomic's database as an immutable value to run at scale
summary
Shows how Datomic turns the database into an immutable, time-aware database used with Clojure on the JVM to run NewBank: 3000+ Datomic databases, 4000 microservices, ~3000 engineers, 100M+ daily users, and >70 billion Kafka events/day. Explains the append-only value-oriented model, how queries can snapshot and replay past states, how auditability and in-memory test DBs simplify incident response and testing, and gives concrete examples of production wins at scale.
AI-written summary · about
chapters (9)
- 0:00Introduction and personal journey
- 10:10Philosophy behind tools like Clojure and Datomic
- 18:23Clojure’s design and immutability
- 23:23Datomic’s immutable database model
- 27:56Benefits of immutable storage in fintech
- 34:34Composability and separation of concerns
- 41:59Scalability and team autonomy at Nubank
- 47:40When to consider Clojure and Datomic
- 49:52Q&A and resources
related talks
28mDatomic at Nubank, Simplicity Scaled
42mDatomic: Challenges and Benefits of an Immutable Database
26m"Operating Datomic at Scale"
41mExploring four hidden superpowers of Datomic
51mDatomic
40mThe power of Datomic database
40mDatomic: The Most Innovative DB You've Never Heard Of
37m11 insights after 11 years with the functional database Datomic
