Admiral Scales Globally with YugabyteDB on GCP + Single-Digit Latency
summary
Admiral migrates from NoSQL to YugabyteDB on GCP to serve publisher account data with global single-digit reads, running a Go microservice stack across 5 regions, 3 continents with two instances per region, RF=3 and three US masters plus regional read replicas. Deployment uses Ansible on SSD persistent disks with TLS and encryption at rest, a Go CQL driver patch to prefer one replica, and achieves 50th <3ms, 90th = 5ms reads at 4000 QPS peak while 90th writes are ~230ms.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:12What does Admiral do?
- 2:12Publishers are building first-party relationships
- 4:00Admiral Accounts
- 5:38Our Tech Stack
- 6:39Requirements
- 9:03Previous Attempts
- 12:57Solution: YugabyteDB
- 16:24Implementation
- 18:48Performance
related talks
19mHow Admiral Scales YugabyteDB Effortlessly on Google Cloud
30mFrom monolith to petabyte scale: Built a cloud-native, AI-ready data layer
26mA Winning Multi Cloud Data Strategy
29mEnterprise Scale: How a Distributed Architecture Can Deliver Scale and Resilience
57mNo Downtime, No Limits
30mBuilding Cloud Native Applications on Distributed SQL Platform
30mTechnical Comparison of YugabyteDB with Oracle and PostgreSQL
25mDiscover the Easiest Path to Distributed DBaaS: Yugabyte Cloud
