3 ms·
This is what I've always done. Databases (or cattle, how or what ever they may be) are always created as a separate stack in your IaC of choice. The values you
by LilBytes 5y ago
This is what I've always done.
Databases (or cattle, how or what ever they may be) are always created as a separate stack in your IaC of choice. The values you need for this stack are always outputted for consumption into other pipelines.
The benefit being you can make lots of small changes to your upstream stacks without breaking your database. And you can place additional controls around the database stack to prevent instance replacement from occurring.
- phaemon 5y ago> Databases (or cattle, how or what ever they may be) It's a reference to the idea that you should treat your servers as "cattle, not pets". In other words, they're disposable and you should be fine with destroying one and creating a new one to take its place. The parent is saying that it's fine to treat databases more like pets, where they're pampered and looked after carefully, and fed treats - much like DBAs are, I believe.