Technical experimentation, discovery, and musings.
Ok, you're back. I'm confident one of the first questions you are going to be asking is, "Why are you writing another article to define 'devops', you already did that." Well, to clarify, I did not define devops, I described it. Now, I am going to actually give you what everyone in the industry has been in search of. An actual, real life definition for the craze 'devops'.
What is DevOps? We hear the term almost daily. It has taken the industry hostage, and yet, there is a great deal of confusion as to what it really means.
Before we dive in to what DevOps is, let's clarify what it isn't. DevOps is not magic. It is not hocus pocus, mystical powers granted to select engineers that fixes all of your problems with little to no effort. DevOps is not perfect, nor is DevOps easy.
Push, or pull? That is the question of the day.
What is push and what is pull? These are simple principles, but can be difficult to explain so I am going to use monitoring to do that for me.
Now here is an interesting topic; one that very few have any understanding or idea what it actually means. What exactly is DevOps?
Ask any modern technology based company if they have a DevOps team, and they will probably say yes. Ask that company to describe DevOps and you will be amazed by how varied the answers are.