DynamoDB

“CloudFront, Lambda, S3, DynamoDB, and IPv6 support are all best-in-class.”

“DynamoDB is really a fantastic product for the 99% percentile of workloads”

“DDB can take upwards of 30 seconds to a minute if you're adding GSIs, but it's a very small tax”

“AWS is good at operations, i.e. running something like S3 at massive scale”

“a great product in a comparatively small niche, and a "meh" premature optimisation pretty much everywhere else”

“Most of the pain that comes from Dynamo is people who try to use it as a primary datastore”

“The 400KB limit is indeed very limiting -- I had to truncate some data because of that.”

“you never have to worry about it in terms of maintenance, admin or scale”

“dynamodb pricing is not cheap but comparatively reasonable. It really is a good product if you know how to use it.”

“If I build on DynamoDB vs RDS I can save 10x.”

“In such a case DynamoDB works and scales amazingly.”

“scales better than anything else at the tradeoff of not guaranteeing durability”

“I've yet to see an OLTP problem that can't live in something like Dynamo.”

“If your problem fits into the dynamo approach (I'd argue that more problems do), then you should be using it.”

“Dynamo scales writes horizontally with the keyspace, forever.”

“one would have to use a distributed cloud database, e.g. AWS Aurora or AWS DynamoDB”

“DynamoDB handled >100M qps during prime day, and its storage is effectively infinite.”

“it's not having to worry about DB uptime, performance, or version updates that keeps me reaching for DDB”

“It solved large scale problems beautifully, much better than SimpleDB”

“built highly scalable, available and near maintenance-free systems using DynamoDB for a ridiculously low cost”

“it excels at stuff like user specific histories that are well partitioned”

“I would not build in DynamoDB if you suspect your access patterns will drastically change over the lifetime of the application”

“DynamoDB is pretty nice if you understand how it's meant to be used”

“Great availability and no operational overhead. Cost was pretty minimal too each time I've used it”

“S3 and DynamoDB are ones that somewhat lock us in”

“lets add more lock-in, why don't you use this tool to optimize your costs (welcome DynamoDB)”

“Fast writes at great scale, But costs set sail, And consistency wasn't what it seemed.”

“someone not doing a back of the envelope guesstimate about how much DyanmoDB would cost to run their payments system on it”

“DynamoDB is almost never a good default choice unless you've thought very carefully about your current and future use cases.”

“knowing very well that was the worse database to use since it does no aggregation type queries”

“a myriad of intermediate steps are introduced to write data to dynamo/s3/kinesis + sqs/and coordination”

“having a local simulator (DynamoDB, Spanner, others) helps me a lot for offline/local development and CI”

“Redis and Dynamo are NoSQL genius, and I said NoSQL the entire time.”

“They use redis, dynamo, scylla or any number of enriched KV stores.”

“DynamoDB is admittedly very verbose, but it's almost always worth it to keep your CRUD operations written within the SDK rather than as an abstraction.”

“just use the native NoSQL in your cloud, e.g. DynamoDB in AWS”

“the way our software works is 95% cheaper to run using S3 as the storage rather than DynamoDB”

“DynamoDB and Spanner are both great, but they're meant to be run by a single admin.”

“both of which have been in full-service, reliable operation since 2012”

“people who don't understand how to do a single table design with DynamoDB”