The no. of partitions in a DynamoDB table goes up in response to increased load or storage size, but it never come back down, ever. DynamoDB is pretty great, but as I have seen this particular problem at 3 different companies — Gamesys, JUST EAT, and now Space Ape Games — I think it’s a behaviour that more folks should be aware of. Credit to AWS, they have regularly talked about the formula for working out the no. of partitions at sessions. DynamoDB Deep Dive However, they often forget to mention that the DynamoDB will not decrease the no. of partitions when you reduce your throughput units. It’s a crucial detail that is badly under-represented in a lengthy guide. Best Practice Consider the following scenario: you dial up the throughput for a table because there’s a sudden spike in traffic or you need the extra throughput to run an expensive scan the extra throughputs cause DynamoDB to increase the no. of partitions you dial down the throughput to previous levels, but now you notice that some requests are throttled even when you have not exceeded the provisioned throughput on the table This happens because there are due to the increased no. of partitions. It translates to higher likelihood of exceeding read/write throughput on a per-partition basis (even if you’re still under the throughput limits on the table overall). less read and write throughput units per partition than before When this dilution of throughput happens you can: migrate to a new table specify higher table-level throughput to boost the through units per partition to previous levels Given the difficulty of table migrations most folks would opt for option 2, which is how JUST EAT ended up with a table with 3000+ write throughput unit despite consuming closer to 200 write units/s. In conclusion, you should in response to temporary needs, it can have long lasting cost implications. think very carefully before scaling up a DynamoDB table drastically Like what you’re reading? Check out my video course and learn how to run a serverless application in production. Production-Ready Serverless We will cover topics including: authentication & authorization with API Gateway & Cognito testing & running functions locally project organization strategies CI/CD centralised logging monitoring distributed tracing with X-Ray tracking correlation IDs performance & cost optimization error handling config management canary deployment VPC security leading practices for Lambda, Kinesis, and API Gateway and include all the latest changes announced at the recent AWS re:Invent conference! _See it. Do it. Learn it! Production-Ready Serverless: Operational Best Practices introduces you to leading patterns and…_bit.ly Production-Ready Serverless

Beware of dilution of DynamoDB throughput due to excessive scaling

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

6 Tips To Scale an AppSync Project To 200+ Resolvers That Will Blow Your Mind

101 Stories To Learn About Cloud Infrastructure

10 Things in Engineering We Don't Spend Enough Time On

10 Things I Did To Increase CloudTrail Logs Security

10 reasons to give cloud computing a go

10 Lessons from 10 Years of AWS (part 1)

6 Tips To Scale an AppSync Project To 200+ Resolvers That Will Blow Your Mind

101 Stories To Learn About Cloud Infrastructure

10 Things in Engineering We Don't Spend Enough Time On

10 Things I Did To Increase CloudTrail Logs Security

10 reasons to give cloud computing a go

10 Lessons from 10 Years of AWS (part 1)

Light-Mode

Classic

Newspaper

Minty

Dark-Mode

Neon Noir

Minty

HN StartUps