Completed
Understand performance implications before using collection types
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Building Financial Systems on Eventually Consistent DBs
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 Billing Engineering
- 3 Netflix operates out of multiple AWS regions to ensure availability
- 4 Single Master Single Point of Failure
- 5 Read replicas
- 6 Slave Promotion
- 7 We needed something better...
- 8 But it's not perfect, especially for a financial system
- 9 So how do you build a financial system on top of it?
- 10 Lightweight Transactions in Cassandra
- 11 Update Consistency With Optimistic Locking
- 12 Two Scenarios
- 13 With Cassandra, last write wins
- 14 How does Cassandra achieve fault tolerance?
- 15 Local Quorum vs Each Quorum
- 16 Insert Consistency
- 17 Some things to consider
- 18 Minimizing inconsistencies
- 19 Building a financial system on top of Cassandra
- 20 Our object model needed relations
- 21 We built a poor man's relational schema
- 22 Understand performance implications before using collection types
- 23 Querying across rows
- 24 Recap
