-
-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add schedule scaling possibility #74
Conversation
@antonbabenko Do you maybe have time to share your opinions on that, please? |
@antonbabenko Can you maybe have another look at it, please? Please let me know what you think 🙂 |
@antonbabenko Just a friendly reminder that I'm still looking for another review :) |
This PR has been automatically marked as stale because it has been open 30 days |
This PR was automatically closed because of stale in 10 days |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
Additionally, it would be nice to use schedule scaling for ddb tables. (https://docs.aws.amazon.com/autoscaling/application/userguide/get-started-exercise.html)
If you want to save cost with PROVISIONED but have for example an import job that needs a lot of capacity it's the only option to not run into scaling issues.
Motivation and Context
If you want to save cost with PROVISIONED but have for example an import job that needs a lot of capacity it's the only option to not run into scaling issues.
Breaking Changes
No, as it is only an additional option.
Draft
This is just a draft of how It could be implemented. I'm open to superior solutions as I know its kinda bad practice.
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request