Any service can go down for whatever reason. In this case, DynamoDB Tables might no longer get any traffic. If an outage lasts long enough, provisioning might scale down to the min-provisioned-values. Since it makes sense to increase provisioning in smaller steps (since upscale-requests are not limited), it might take a long time after such an outage to get the table provisioning back to the required "normal" level.
Idea: Allow configuring a URL and max-response-time that is checked every check-interval before the dynamic-dynamo does its magic.
This might be a simple api endpoint that returns 200 if the service is up. If it responds, the script does its magic. If it does not return 200 or responds too slow, dynamic-dynamodb should stop downscaling the provisioning to allow speedy retrun to production throughput after an outage.
Added configuration options for #25
Updated example config and docs for #25
Wrote circuit breaker code for #25
Feature now released in version 1.2.0. Use the following settings under [global] to configure the circuit breaker:
Support for basic authentication is provided via the circuit-breaker-url parameter. Use a URL like this https://username:firstname.lastname@example.org/api/status to make a BA call.