4 ms·
So they switch from one giant RDS instance with all tenants per AZ to per-tenant PG in Kubernetes. So really we don’t know how much RDS was a problem compared
by MBCook 4y ago
So they switch from one giant RDS instance with all tenants per AZ to per-tenant PG in Kubernetes.
So really we don’t know how much RDS was a problem compared to the the tenant distribution.
For the purposes of an article like this it would be nice if the two steps were separate or they had synthetic benchmarks of the various options.
But I understand why they just moved forward. They said they consulted experts, it would also be nice to discuss some of what they looked or asked about.
- raffraffraff 4y agoYeah. I mean, if you're going to use AWS database service for this use case, something that automatically scales based on load makes more sense, like Aurora Serverless. But that's also expensive. Regardless of cost, plain RDS isn't the right solution here as all.
- eptcyka 4y agoYes, that's basically the whole point of the article - an assumption they may not have made all too consciously to use RDS turned into a bad decision they sought to rectify.