Update provisioning in units not just percentage

[fwachsmuth]

For some table's access patterns, scaling the table in percent does not make sense and scaling by fixed amounts would make more sense.

Growth of table traffic isn't always exponential but can also be linear.

[sebdah]

Thanks, this is a thing I've been having in the back of my head, but I haven't seen the use for it myself. Good to know that your use case needs it. Added it to the feature request pool.

[fwachsmuth]

What might make even more sense: Upscale by required amount (or a percentage of that). E.g. if consumed reads are 140% (you know dynamodb allows some grace bursts since a while) upscale by 40% (or 50% of that -- thus 20%)

[sebdah]

A quick update. The code refactoring made prior to the 1.0.0 release has been made with this feature request in mind. Will have a look later on to see how to implement this best.

[sebdah]

This feature has been fixed in version 1.1.0. Four new properties has been added:

• increase-reads-unit
• decrease-reads-unit
• increase-writes-unit
• decrease-writes-unit

All of those options takes either percent or units. If it is set to units Dynamic DynamoDB will scale up/down in units rather than percent.

No support for sensing buffer usage for now, unfortunately.