Amazon DynamoDB

33 engineers on Hacker News describe using Amazon DynamoDB first-hand: 6 endorse it, 3 regret it, 4 are mixed.

61%trust
33first-hand users
32in production
endorse 6mixed 4regret 3uses, no opinion

“we started with DynamoDB for our metadata store, but our access patterns kept running into per-partition throughput limits.”

regret · production · quettabit · 2025-12-08 · source ↗ · wrong label?

“I just spent 8k USD on writing 2 billion rows to two tables because I misunderstood how Dynamo charges for write units.”

regret · production · efxhoy · 2023-05-26 · source ↗ · wrong label?

“we just didn't need one for the new Dynamo stuff.”

endorse · production · pwinnski · 2022-09-29 · source ↗ · wrong label?

“DynamoDB fits fairly well in the microservices world where the service scope is small... Building new things using DynamoDB when query patterns aren't necessarily known is very painful”

mixed · production · sakopov · 2022-01-20 · source ↗ · wrong label?

“We realized how great Dynamo was only after we migrated off AWS.”

endorse · production · artembugara · 2022-01-20 · source ↗ · wrong label?

“So at some point we migrated parts of it to Dynamo, and poof all of our problems went away, including operational ones.”

endorse · production · mxz3000 · 2021-10-03 · source ↗ · wrong label?

“DynamoDB didn't work with Django's ORM and was surprisingly expensive”

regret · personal · The_Amp_Walrus · 2019-07-28 · source ↗ · wrong label?

“Dynamodb is better in cases where we want to localize the latency of our regional lambdas.”

endorse · production · InGodsName · 2018-12-26 · source ↗ · wrong label?

“DynamoDB is the most expensive one. For small datasets with low RPS it provides a lot of value, but once you scale, it becomes cheaper to run ouselves”

mixed · production · LaserToy · 2018-12-15 · source ↗ · wrong label?

“We process a lot of incoming data and dump most of it into dynamo... Lock-in makes me nervous, and the way it scales up/down really makes it difficult to use it for hourly workloads”

mixed · production · orthecreedence · 2018-11-28 · source ↗ · wrong label?

“My biggest complaints are probably DynamoDB eventual consistency (unavoidable when using GSIs)”

mixed · production · 1.5 yr · not_kurt_godel · 2018-06-23 · source ↗ · wrong label?

“We use DynamoDB at my place. We had to make some tooling around it and figure out some growing pains, but now we have an extremely scalable solution.”

endorse · production · dyeje · 2017-11-30 · source ↗ · wrong label?

“For example, we use DynamoDB for saving build and release records. ... Amazon is keeping DynamoDB Available, you don't have to manage an etcd cluster”

endorse · production · nzoschke · 2015-08-02 · source ↗ · wrong label?

“We have a similar story with DynamoDB too.”

neutral · production · nusmella · 2023-08-10 · source ↗ · wrong label?

“we switched to using a little URL shortening service that we wrote on aws lambda+dynamodb”

neutral · production · tonto · 2023-01-09 · source ↗ · wrong label?

“Cloud Tech (AWS) which also includes, lambdas, Iam management, dynamoDB, cdk or serverless”

neutral · production · _gabe_ · 2022-12-10 · source ↗ · wrong label?

“On AWS we prefer using things like DynamoDB and that further locks us into AWS.”

neutral · production · eknkc · 2022-09-29 · source ↗ · wrong label?

“there are plugins for running the lambdas locally as well as for dynamodb, sqs, ses and eventbridge.”

neutral · production · wdfx · 2021-12-03 · source ↗ · wrong label?

“These are the services we used.”

neutral · production · scarface74 · 2020-12-20 · source ↗ · wrong label?

“Our terraform has infrastructure code for: API Gateways ... DynamoDB tables”

neutral · production · lovehashbrowns · 2020-10-12 · source ↗ · wrong label?

“Our user generated content (more like 2-3x read vs write) is all backed by DynamoDB”

neutral · production · phamilton · 2020-04-04 · source ↗ · wrong label?

“We use Aurora (with autoscaled readers) and DynamoDB (autoscaled IOPS).”

neutral · production · phamilton · 2019-12-19 · source ↗ · wrong label?

“It can also be used in Dynamodb which is what we use in adtech.”

neutral · production · InGodsName · 2018-12-28 · source ↗ · wrong label?

“We have an existing production system that uses a combination of SQS, DynamoDB, and Postgres, and EC2s”

neutral · production · bballer · 2018-11-28 · source ↗ · wrong label?

“We generally run our tables with autoscaling set to 70% of capacity, so at $0.18 per million write requests our effective cost is $0.25”

neutral · production · phamilton · 2018-11-28 · source ↗ · wrong label?

“The GraphQL API is backed by DynamoDB and is served via API Gateway.”

neutral · production · leetbulb · 2017-12-05 · source ↗ · wrong label?

“we migrated all of our high volume data into other stores-- analytics into DynamoDB, searchable data into ElasticSearch, etc.”

neutral · production · jkodumal · 2016-09-09 · source ↗ · wrong label?

“we migrated a key piece of our analytics infrastructure over to DynamoDB, for example, and controlled the rollout of that via a feature flag.”

neutral · production · jkodumal · 2016-04-13 · source ↗ · wrong label?

“And, I'd say that using Dyanamo as a DB locks you much more securely into AWS than API Gateway and Lambda.”

neutral · production · cargomaster · 2015-07-16 · source ↗ · wrong label?

“We're using Dynamo for storage.”

neutral · production · jeletonskelly · 2015-07-08 · source ↗ · wrong label?

“We've written a library for interacting with DynamoDB and Amazon Kinesis”

neutral · production · benwilson513 · 2015-01-26 · source ↗ · wrong label?

“have been using more and more ACTUAL AWS services (SQS, DynamoDB, Redshift)”

neutral · production · atonse · 2014-12-19 · source ↗ · wrong label?

“I use DynamoDB when I have extremely high dataloads.”

neutral · production · nielskrijger · 2014-10-19 · source ↗ · wrong label?