2 ms·
This is just the tip of the iceberg with DynamoDB's pricing issues. Based on my understanding of how their pricing works, here are two more major issues: -You
by the_bear 15y ago
This is just the tip of the iceberg with DynamoDB's pricing issues. Based on my understanding of how their pricing works, here are two more major issues:
-You have to provision throughput for each table individually, so you basically have to pay for the maximum throughput you expect for every single table all the time (you can only reduce your throughput once per day as far as I understand). This means that adding a new table can be pretty expensive (even if your total throughput isn't increasing at all).
-Each unit of throughput gives you one 1kb write/read per second. If you exceed your throughput for a second, the call fails. This means that if you want to support the ability to write 50kb (like a "notes" field or something), you need to constantly pay for 50 write units even if you won't ever realistically use that much. And you have to do that for every single table
As the OP points out, it's all about FUD. I'm so terrified of exceeding my throughput allotment that I'm forced to pay for an order of magnitude more resources than I will actually use. This seems to go against everything AWS is about.