Menu

Why your DynamoDB app got slow as data grew
πŸ“°

Why your DynamoDB app got slow as data grew

DEV Community: awsΒ·Ivan DolgovΒ·3 days ago
#cXo2QIO5
#devtoaws#devto#dev#list#scan
Reading 0:00
15s threshold

The complaint usually arrives in the same shape. The product was fine. Nobody changed the architecture. And now a list screen takes nine seconds, the mobile app times out on export, and it is getting worse every month β€” for everyone, not for one customer on one screen.

Nothing broke. That is the part worth sitting with, because it decides where you look.

00 / Growth does not break a data model. It reveals one.

A data model encodes the assumptions of the weeks it was written in: how many records there would be, how many tenants, which screens would read what. Those assumptions are rarely written down, and they are never wrong on day one β€” there is not enough data for them to be wrong yet.

What changes is the volume, and volume turns a constant-time mistake into a linear one. A full table read costs nothing at a thousand items. At a hundred thousand it is the product.

So the question is not "what regressed?" Nothing regressed.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.