DevOps

As a developer and architect, I am VERY proud of having spent a few years of my life doing production support. Having been "on the other side of the barricade" gives you great clues on how an application should be conceived to avoid operational nightmares.

So, welcome to DevOps.

Here a link to a great post on the topic:

http://blog.carlossanchez.eu/2012/01/02/about-devops/

http://en.wikipedia.org/wiki/DevOps generalities on DevOps
http://theagileadmin.com/2010/10/15/a-devops-manifesto/ a DevOps Manifesto

« Infrastructure is code, and should be developed and managed as such.”
“Simplicity–the art of maximizing the amount of work not done–is essential.”


“Giving developers more environment control »
« Automating as much as possible”
“Collaboration between dev and ops »

“iterative development ... each release has less change but occurs more often. This creates a smooth rate of progressive application change vs. the large impact effect of rare deployments–each of which contains a large number of changes.”


(carefully avoiding here the word “agile” because a too overloaded word)



Thinking in silos: