Since the last release of this project, DynamoDB now supports a new billing mode of "Pay Per Request", which sets your DynamoDB table as on-demand. Previously the default setup was to create a Table with a provisioned throughput of 10. If you are creating multiple tables (especially for testing purposes), this can increase your AWS costs significantly. You can read more about this change here
This check-in will set default table creation as PAY_PER_REQUEST unless provisionedThroughput is called.
Code Changes
On default table schema generation, set the BillingMode attribute to PAY_PER_REQUEST, which will set the read/write capacity mode of the table to on-demand by default
When calling the .provisionedThroughput or setting the ProvisionedThroughput attribute on migration table creation, we set the BillingMode back to PROVISIONED
Update default schema setup to prevent using the same config for both secondary index and table creation and not provide a BillingMode unless one is specified (i.e. it is only set when creating a table)
Since the last release of this project, DynamoDB now supports a new billing mode of "Pay Per Request", which sets your DynamoDB table as on-demand. Previously the default setup was to create a Table with a provisioned throughput of 10. If you are creating multiple tables (especially for testing purposes), this can increase your AWS costs significantly. You can read more about this change here
This check-in will set default table creation as PAY_PER_REQUEST unless
provisionedThroughputis called.Code Changes
BillingModeattribute toPAY_PER_REQUEST, which will set the read/write capacity mode of the table to on-demand by default.provisionedThroughputor setting theProvisionedThroughputattribute on migration table creation, we set theBillingModeback toPROVISIONED