How Charles Schwab Uses Aerospike as an Intraday System of Record
summary
Charles Schwab moves trading front ends off mainframe and uses Aerospike as the intraday system of record, achieving 30 ms average latency and 2 million transactions per minute for transaction processing. Architecture keeps DB2 as legacy SOR while new flows write to Aerospike first and replicate to DB2 asynchronously, deployed across four zones with a Zone Isolation strategy and Kafka bridging; operational scale is about 150 TB per zone and roughly 75 billion daily transactions.
AI-written summary · about
chapters (11)
- 0:00Aerospike at Charles Schwab
- 1:47Mainframe limitations in 2014
- 3:14Modern trading demands
- 4:44Decoupling apps from Mainframe
- 6:54Migrating read apps
- 7:58Write-first transaction paradigm
- 8:44Aerospike as system of record
- 9:49Zone isolation strategy
- 10:52Aerospike performance metrics
- 12:17Three phases of adoption
- 13:44Modernization results and plans
related talks
40mDeveloping highly scalable applications with Aerospike
31mUnlocking the value of your SOR data in regulated industries
28mFireside Chat with Charles Schwab: Expanding Modernization from Applications to Databases
48mThe real-time database to build your AI future
32mBuilding a Real-time Ingestion Platform using Kafka and Aerospike
33mInnovation with Aerospike: How AppLovin Handles Billions of Requests per Day
49mJourney with Aerospike: Architecture Best Practices
33mUsing Aerospike as a Real-time System-of-Record for Adobe Experience Cloud Services on Azure