You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cloud.gov's current billing model is not conducive to be being able to scale due to increases in demand. Forget about auto-scaling, even if a few big partners suddenly joined and wanted to start using Notify it would take weeks/months to change our agreement with cloud.gov so that we would have capacity to scale horizontally.
It's also not even clear at this time what the scaling options our. We are currently one step below the max db size that has been revealed to us. Are there larger sizes beyond that? Ditto for Redis.
Presumably increasing capacity with cloud.gov would increase our ability to scale horizontally, but it's not very comforting when the alternative (auto-scaling) would be something we could easily test and fine-tune in real time just by doing a big load test.
The text was updated successfully, but these errors were encountered:
Cloud.gov's current billing model is not conducive to be being able to scale due to increases in demand. Forget about auto-scaling, even if a few big partners suddenly joined and wanted to start using Notify it would take weeks/months to change our agreement with cloud.gov so that we would have capacity to scale horizontally.
It's also not even clear at this time what the scaling options our. We are currently one step below the max db size that has been revealed to us. Are there larger sizes beyond that? Ditto for Redis.
Presumably increasing capacity with cloud.gov would increase our ability to scale horizontally, but it's not very comforting when the alternative (auto-scaling) would be something we could easily test and fine-tune in real time just by doing a big load test.
The text was updated successfully, but these errors were encountered: