DynamoDB 10 years later

Re:DynamoDB 10 years later by manishsharan on Thursday January 20, 2022 @09:15AM (#30009154)

Quite a few of the teams that were early adopters of AWS DynamoDB were not prepared for the pricing nuances that had to be taken into consideration when building their solutions.

[ Parent | on HN ]

Re:DynamoDB 10 years later by xtracto on Thursday January 20, 2022 @09:45AM (#30009498)

I remember trying Dynamodb around 2015/2016: You had to specify your expected read and write throughout and you would be billed for that. At that time we had a pretty spikey traffic use case which made using dynamodb efficiently impossible

[ Parent | on HN ]

Re:DynamoDB 10 years later by musingsole on Thursday January 20, 2022 @09:53AM (#30009585)

I had a similar experience, but ultimately wrote a service to monitor our workloads and request increased provisioning during spikes. You could reduce your provisioning like 10 times a day, but after that you could only increase it and would be stuck with the higher rate for a time.

And then on-demand provisioning was released and it was cheap enough to be worth simplifying our workflows.

[ Parent | on HN ]

Re:DynamoDB 10 years later by jvanvleet on Thursday January 20, 2022 @10:13AM (#30009855)

I was one of these. However I now understand that the pricing nuances reflected a reality that I appreciate. We used DDB in a way that was not the best fit and the cost was a reflection of this.

[ Parent | on HN ]