If you allow every product delivery team to choose which type of bolt they want to use, you might end up with half the teams using hex heads and half using phillips.
This means that now every infrastructure engineer has to carry a set of screwdrivers AND a set of allen keys. 😟
This means that now every infrastructure engineer has to carry a set of screwdrivers AND a set of allen keys. 😟
Giving delivery teams autonomy is great and all, but there exist a set of decisions which:
a) don't really impact a single team either way, but
b) have non-trivial repercussions in the aggregate
There's leverage in replacing these decisions with one standard approach.
a) don't really impact a single team either way, but
b) have non-trivial repercussions in the aggregate
There's leverage in replacing these decisions with one standard approach.
Some examples I've seen:
- Every service serves HTTP on the same standard port
- Every service gets its DB connection string via the same mechanism (e.g. a DB_CONN env var)
- Don't have services on MySQL 5.5, 5.6, and 8
- Every service serves HTTP on the same standard port
- Every service gets its DB connection string via the same mechanism (e.g. a DB_CONN env var)
- Don't have services on MySQL 5.5, 5.6, and 8
an extreme example I've seen:
Don't have half of your infra in AWS and half in GCP because some teams preferred AWS and some preferred GCP.
Don't have half of your infra in AWS and half in GCP because some teams preferred AWS and some preferred GCP.
