Skip to content
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

[Feature] Minimum Subnets: 3 #7969

Open
todd-dsm opened this issue Sep 14, 2024 · 0 comments
Open

[Feature] Minimum Subnets: 3 #7969

todd-dsm opened this issue Sep 14, 2024 · 0 comments
Labels
kind/feature New feature or request

Comments

@todd-dsm
Copy link

What feature/behavior/change do you want?

I'd like to suggest the minimum number of subnets be changed from 2 -> 3; docs.

Why do you want this feature?

The SRE Handbook describes Capacity Planning like:

Provision to handle a simultaneous planned and unplanned outage, without making the user experience unacceptable; this results in an "N + 2” configuration, where peak traffic can be handled by N instances (possibly in degraded mode) while the largest 2 instances are unavailable.

While they are specifically describing nodes, the concept could be expanded to mean any fundamental resource. Given a stellar (but imperfect) history of AWS' uptime, it seems that three (3) would be an improved number to suit the foundational concept of a distributed system.

In this way, we could be slightly better off knowing that we could withstand an unplanned outage in the middle of a planned outage.

What say the council?

@todd-dsm todd-dsm added the kind/feature New feature or request label Sep 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant