3 ms·

Is it? Every solution has some advantages, switching between them is relatively easy (especially if you can tolerate some writing downtime), and IMO it's not th

Is it? Every solution has some advantages, switching between them is relatively easy (especially if you can tolerate some writing downtime), and IMO it's not that confusing if you have at least some experience in the space. Otherwise if you're just staring from scratch, I'd pick provisioned aurora if your load is steady and serverless v2 if not. Then IO optimized if the db doesn't fit into memory and non-IO-optimized until it does.

zokier 2y ago
It's not just selecting the service. It's also trying to decipher which parts what docs apply to when reading. Or how different services interact. Or getting any understanding what "Aurora" means in different contexts. Just random example I was poking around AWS Backup recently, and there you have option to enable Backup for different services. Among the other options, you have separate toggles for "Aurora" and "RDS". Overall the whole RDS API has lots of weirdness because there are all these different things (and combinations of things). Another random example, configuring Data HTTP API, you got this thing: https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_EnableHttpEndpoint.html https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/AP... > This operation applies only to Aurora Serverless v2 and provisioned DB clusters. To enable the HTTP endpoint for Aurora Serverless v1 DB clusters, use the EnableHttpEndpoint parameter of the ModifyDBCluster operation. At least that specific case was nicely documented now. Not all the pitfalls are thst clear.