One-click deployment does not really exist
On vend souvent le déploiement en un clic comme le but ultime. J'ai passé assez d'années dans les salles de mise en production pour savoir que ce bouton unique cache toujours des dizaines de décisions prises en amont. Le clic est la partie facile. Tout ce qui le rend sûr, c'est le vrai travail, et il est invisible depuis le bouton. Ma priorité en ingénierie de livraison n'a jamais été la vitesse,…
Sergey Shinder discusses the importance of reversibility in deployment engineering. He prioritizes being able to roll back changes in case something goes wrong over speed. Shinder prefers gradual deployments, where a new version is sent to a small percentage of users first, to minimize potential damage. He also emphasizes the need for careful planning in database migrations to ensure compatibility and the ability to revert changes. The goal, he says, is to make deployments predictable and easy to reverse.
Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.
