4 ms·
Fair. But it doesn't really explain why they wanted to stay on RDS. This is their reasoning: > over the past few years, we’ve developed a lot of expertise on h
by mbesto 3y ago
Fair. But it doesn't really explain why they wanted to stay on RDS. This is their reasoning:
> over the past few years, we’ve developed a lot of expertise on how to reliably and performantly run RDS Postgres in-house. While migrating, we would have had to rebuild our domain expertise from scratch.
So they had in house expertise to run performantly on RDS but that same experience couldn't be translated to switching over to it running on EC2 + Citus? Rather they used another non-experience concept of building their own sharding? That left me scratching my head.
- lopkeny12ko 3y agoI was puzzled by this as well. RDS is a managed, cloud product. You don't run it. The whole point is that AWS runs it for you, no?
- thih9 3y agoIt’s Postgres, large dbs will need some level of config and maintenance. > Common DBA tasks for Amazon RDS for PostgreSQL https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.PostgreSQL.CommonDBATasks.html https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appen...
- thih9 3y agoPerhaps there were legal, compliance, or contractual constraints that made moving out of RDS impossible within their acceptable business risk levels?