Developing highly scalable applications with Aerospike
summary
Charles Schwab deploys Aerospike since 2015 as a read cache, an intraday operational store and the system of record for new high-volume apps, handling 13 billion queries per day and delivering 99.9% <1ms reads while keeping service-level targets of ~30–40 ms. Architecture uses .NET object bins, DB2 integration via MQ drainer, NVMe disks (up to 6.2 TB each), rack/XDR multi-datacenter replication, strong consistency, blue/green set swaps for daily refreshes and a live core post‑processing engine since 2018 storing ~120 TB and scaling to 500 TB.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:37Background
- 4:20Strategy
- 7:40Read Applications
- 9:12Migration to Aerospike
- 11:20System of Record
- 20:00Use case 1
- 23:40Benefits
- 24:20Use Cases
- 28:22Business Capabilities
- 31:08Questions
- 32:44Consistency
- 34:43Write process
- 36:58Data storage
related talks
15mHow Charles Schwab Uses Aerospike as an Intraday System of Record
49mJourney with Aerospike: Architecture Best Practices
30mWelcome and the Aerospike Journey
48mThe real-time database to build your AI future
33mInnovation with Aerospike: How AppLovin Handles Billions of Requests per Day
36maccelerating the digital agenda
33mUsing Aerospike as a Real-time System-of-Record for Adobe Experience Cloud Services on Azure
21mCaching Snowflake data with Aerospike for advanced analytics