CASE 143 · PEARL · 2024
Customers in Asia who get the Asia region, automatically.
A B2C mobile app served customers across five continents from a single US-East-1 deployment. Asian customers had been quietly complaining about latency for a year. We added a multi-region active-active deployment with Route 53 latency-based routing.
B2C mobile
RELIABILITY
2024
RESULTS
What changed, by the numbers.
APAC p95 LATENCY
−78%
REGIONS ACTIVE
3
APP STORE RATING
+0.4
DATA REPLICATION
< 1s
HOW IT WENT
The latency problem had become an app-store-rating problem. Reviews from Asia mentioned "slow" disproportionately. The team had been deferring a multi-region investment "until we’re bigger" — but the app was bigger in Asia than anyone had noticed.
We deployed the API surface in three regions: us-east-1, eu-west-1, ap-southeast-1. DynamoDB Global Tables replicated the data within a second across regions; Route 53 latency-based routing sent each request to the closest healthy region. CloudFront in front served static assets from the nearest edge.
APAC p95 latency dropped 78%. The app-store rating in Asian markets improved by 0.4 within a quarter. The team operates the multi-region deployment as a single architecture; the latency-routing handles the rest.
RELATED · SAME DOMAIN
Other engagements in this space.
READY WHEN YOU ARE
Let's get your AWS bill (and architecture) in order.
The discovery call is free. You walk away with at least one concrete idea — even if we never work together.