Brian’s Kindle Notes & Highlights

Practice of Cloud System Administration, The: DevOps and SRE Practices for Web Services, Volume 2, by Thomas A. Limoncelli

A configuration setting (a toggle) should be present to enable or disable each new feature.

It's probably healthy to remove the switches after some time. I haven't seen a good trigger to spark the removal however, other than putting it on the list of what a project's done-done-done criteria. Can be healthy to decide which switches should remain for load-shedding, feature disabling (e.g. If it's broken and affecting other portions of the app somehow), but don't leave them all on forever. Configuration represents opportunity for dev/test/prod env entropy, even when code is identical.

Steve Sarner liked this

See all 7 comments

27 Aug 17 · Flag

Robert Gustavo

Every time you add a switch, you should add a jira task to remove it. Our page of switches is unwieldy.

28 Aug 17 · Flag

Dylan Jackson

Assuming you log/write switching events, detecting switches which have not changed in several months (which are not whitelisted for keeping long-term for operational purposes) is a good way to detect …

28 Aug 17 · Flag

Brian

+1 on Gus. Maybe there's also a periodic active step to review/justify/retain a switch so there's consistent pressure to downsize? Dylan's suggestion can be used to escalate pressure.

See Brian’s 54 notes & 71 highlights