A Decade of Dynamo
allthingsdistributed.com
A Decade of Dynamo
1–10 of 58 posts
Re: A Decade of Dynamo
#2What is the machine in the photo?
Re: A Decade of Dynamo
#3What is the machine in the photo?
A dynamo... ;)
Re: A Decade of Dynamo
#4amazing product
Re: A Decade of Dynamo
#5The thing doesn't even support a useable cross region replication. On top of that the whole read/write capacity is a joke (a painful one at that).
Other than a dirty js config or a prototype store this db is useless.
Re: A Decade of Dynamo
#6I'd be interested to hear how others are handling read/write capacity configuration for dynamo. It seems like it would be very easy to hit the account limit of 10,000 units once you are querying any significant amount of data. I've also run into issues with auto scaling where you have to endure up to 15 minutes of downtime before the scaling kicks in [0]. Even on a table with ~2000 items I've found it becomes quite slow and costly to fetch data. Also the 25 item limit on batch writes makes it pretty frustrating to edit/delete lots of data.
- [0] https://hackernoon.com/the-problems-with-dynamodb-auto-scali...
Re: A Decade of Dynamo
#7I'm more interested in solutions like Spanner and Cockroach. Different tradeoffs for different applications, but they seem to be the most general purpose of the highly scalable databases. DynamoDB is cool and I've tried to adopt it for things, but it's surprisingly hard to imagine an application where the model isn't somewhat limiting. The capacity provisioning is also quite painful, which doesn't help matters any.
Re: A Decade of Dynamo
#8I'd be interested to hear how others are handling read/write capacity configuration for dynamo. It seems like it would be very easy to hit the account limit of 10,000 units once you are querying any significant amount of data. I've also run into issues with auto scaling where you have to endure up to 15 minutes of downtime before the scaling kicks in [0]. Even on a table with ~2000 items I've found it becomes quite s…
You can request that limit be increased through the limit increase form.
Also, if you need to scan a ton of items to assemble your desired result, you should re-think using DynamoDB as a whole.
Re: A Decade of Dynamo
#9I don't know why amazon is so taken with Dynamodb. I find it to be incredibly unintuitive and lacking real world application, requiring applications to perform gymnastics to work with it.
Re: A Decade of Dynamo
#10DynamoDB is amazing for the right applications if you very carefully understand its limitations.
Last year I built out a recommendation engine for my company; it worked well, but we wanted to make it real-time (a user would get recommendations from actions they made seconds ago, instead of hours or days ago). I planned a 4-6 week project to implement this and put it into production. Long story short: I learned about DynamoDB and built it out in a day of dev time (start to finish, including learning the ins and outs of DynamoDB). The whole project was in stable production within a week. There has been zero down time, the app has seamlessly scaled up ~10x with consistently low latency, and it all costs virtually (relatively) nothing.