Amazon DynamoDB
No written verdict yet. Here is what commenters said.
6recommend
3warn against
Nov 3, 2025first mention
Oct 1, 2026latest mention
Why people recommend it
“Cassandra to DynamoDB migration, no downtime.”
“to only allows rows to be accessed based on the user”
Show 3 more
“would benefit from on-demand provisioning”
former AWS service team engineeron “We Rewrote JSONata with AI in a Day, Saved $500K/Year”
“I use DynamoDB almost exclusively.”
“This article ends up making a compelling case for DynamoDB.”
Caveats and dissent
“Horrible horrible choice and after 4 years working on it I dont see why you would.”
4 years working on DynamoDB at Tinderon “I returned to AWS, and was reminded why I left”
“our access patterns kept running into per-partition throughput limits”
Often compared with
Amazon S3Who recommends it in their own words
Threads where it came up
- AWS Acquires DuckLabs 3 mentions
- I returned to AWS, and was reminded why I left 2 mentions
- Ask HN: Who wants to be hired? (October 2026) 1 mention
- Ask HN: What are you working on? (September 2026) 1 mention
- item 48632785 1 mention
- PgDog is funded and coming to a database near you 1 mention
Also written as Amazon DynamoDB. Data: amazon-dynamodb.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 25
“Databases: MySQL, PostgreSQL, MongoDB, DynamoDB, Neon”
“DynamoDB for billing storage”
“DynamoDB has basically two legitimate use-cases that I'm familiar with”
“DynamoDB (The AWS service)”
https://www.amazon.science/publications/dynamo-amazons-highly-available-key-value-store
“Unisondb is dynamodb inspired multimodal database written in go”
“We use it heavily.”
“apigw + lambda + dynamodb stack”
> you have a limited number of global supported indexes, 5 iirc you can create 20 global (GSI) and 5 local (LSI) indexes per table[1], I think the number must have been lower at some point in the past, because it's not the first time I hear this complaint [1] https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-indexes-general.html
“Horrible horrible choice and after 4 years working on it I dont see why you would.”
“Cassandra to DynamoDB migration, no downtime.”
“S3 and DynamoDB are ones that somewhat lock us in”
“DynamoDB and Postgres at least on AWS both have Row level security”
“to only allows rows to be accessed based on the user”
“would benefit from on-demand provisioning”
“I first used DynamoDB 8 years ago”
“I use DynamoDB almost exclusively.”
“Go microservices, DynamoDB, redis”
“Hono.js on Lambda, TypeScript, PostgreSQL, DynamoDB.”
“I may stick with Dynamo or Cloudflare options eventually though”
“This article ends up making a compelling case for DynamoDB.”
“our access patterns kept running into per-partition throughput limits”
“Stack includes Golang, Neo4j, AWS (Lambda, SQS, S3, DynamoDB)”
“implemented on top of DynamoDB”
“Skills: AI agents, Python, Node.js, AWS Lambda, API Gateway, DynamoDB, S3, CloudFormation, Terraform, RDS, Pytest, Docker, Kubernetes”