Hacker News Reader

To be clear, the auto-scaling with provisioned capacity still lags behind demand quite a bit. The new on-demand pricing makes this a non-issue but you pay for it at much higher cost at any sort of sustained load. https://serverless.com/blog/dynamodb-on-demand-serverless/ has a good breakdown of when to use on-demand vs provisioned capacity.

View on HN

Paying in terms of write units adds so much complexity to what would otherwise be dead simple code.

Normally, you just write to a data store until it's done. The faster the disks the less time it takes.

Now, writes can "fail" so you need to wait/retry or put it back on a queue to reprocess when you have write units available (both of those and the associated logging will cost you $ on AWS).

Reply on news.ycombinator.com