We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

We can all have nice things: Patterns for Brownfield Automation

Formale Metadaten

Titel
We can all have nice things: Patterns for Brownfield Automation
Alternativer Titel
We can all have nice things: Patterns for BrownField Automation
Serientitel
Anzahl der Teile
50
Autor
Lizenz
CC-Namensnennung - Weitergabe unter gleichen Bedingungen 3.0 Unported:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen und nicht-kommerziellen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen und das Werk bzw. diesen Inhalt auch in veränderter Form nur unter den Bedingungen dieser Lizenz weitergeben.
Identifikatoren
Herausgeber
Erscheinungsjahr
Sprache

Inhaltliche Metadaten

Fachgebiet
Genre
Abstract
Are you from a large and old IT organization? Do you support legacy applications that were lovingly built by hand in the distant past? Do you want to automate all of the things but feel it’s just not possible because you’re faced with a mountain of technical debt? Or do you think automation is too hard because you simply can’t rebuild your servers because you either don’t know how or because no one will give you new servers? Do you want to have nice things? It’s hard to know where to start a brownfield automation project and how to keep it going once it’s started. Adobe IT Web Platform Services had this problem and still has this problem. We used to build and deploy everything by hand. We had excessive configuration drift. We didn’t exactly know how to rebuild our servers. We would fat finger deployments and cause service outages. We had 19 different environments, all different, and all updates were pushed out by hand. We have a lot of technical debt. We’re better because we’ve tried to automate. We’re not yet completely automated. We don’t do CI or CD. We don’t even do automated tests. But we’re using Chef and our lives are better because of it. We’ve eliminated configuration drift. We’ve made rollout and rollback easier. And yes, we have nice things.