Migrating Primer’s Live Payments Platform to CockroachDB with Zero Downtime
summary
Primer migrates its live payments workload from single-writer Postgres on RDS to CockroachDB with dual-writer application logic, AWS DMS replication and a throttled DMS node to avoid saturating RDS. Hot data lives in CockroachDB while older records are archived to S3 with lazy hydrate on access, cutting storage costs during migration. New payments run on Cockroach by mid‑2023, final RDS shutdown occurs May last year, zero downtime maintained, and some write patterns are reworked to use versioning.
AI-written summary · about
chapters (12)
- 0:00Primer and migration challenge
- 1:09Why Primer needed distributed DB
- 2:53Postgres limitations
- 4:20New DB requirements
- 6:26Zero-downtime strategy
- 7:50Dual-writer model process
- 8:32Cold data archiving
- 9:33Final cutover benefits
- 10:36Upgrades improvements
- 11:38Migration learnings
- 13:02Cost model future plans
- 13:48Q&A
related talks
28mGlobal Payments: Subsecond Performance Worldwide
23mWhy Squarespace adopted CockroachDB for better global performance at scale
15mScaling to support America’s #1 sportsbook
31mFuture-proofing operational data at scale
14mBuilding CockroachDB for performance at scale
48mBuilding mission-critical applications with CockroachDB
15mScaling to support America’s #1 sportsbook
24mNavigating Distributed Databases: Challenges & Opportunities