3 ms·
The missing piece in all of this is the possibility of a clean rollback. If all infrastructure could be described "as code" and is version controlled in Git or
by ofrzeta 9y ago
The missing piece in all of this is the possibility of a clean rollback. If all infrastructure could be described "as code" and is version controlled in Git or something you could roll back. That doesn't take into account the omnipresent state in databases and so on. I have yet to see a system or environment that doesn't save state in databases or similar systems.
- jnsaff2 9y agoWell, we are moving towards more statelessness in infrastructure, meaning the state is only stored in databases and the rest of the infrastructure does not (or should not) contain any state. So you can have immutable servers which you can replace and upgrade/downgrade at will with much less worry about state. You still need to care about the databases but it is much more confined.