A (True) Story of DevOps

One day Mickey was at the coffee shop when he saw Minnie on the street

Mickey – Hey Minnie

Minnie – Hi Mickey, How are you?

Mickey – I am good, what are you doing here?

Minnie – I came to get some books on DevOps, you see I keep on hearing this word a lot and now I need to understand in real terms what exactly is DevOps

Mickey – Okay, Do you want to hear a real interesting story of DevOps

Minnie – Wow, Yes, Please tell me

Mickey – Let’s go to the coffee shop then

Minnie – Sure, Let’s go



(Mickey starts the Story)

Mickey – Once upon a time there was Tom and Jerry

Minnie – I know them

Mickey – Wait! The story has just begun. In our story, Tom is a boy and Jerry is a girl

Tom and Jerry worked in a company. Tom was a developer and Jerry was a System Admin in the Operations team

Minnie – So Tom was Dev and Jerry was Ops

Mickey – Yes

So Tom (dev) writes code and Jerry (ops) is responsible to deploy code into production and maintain servers, configuration, etc

Minnie – I am getting this

Mickey – Tom & Jerry have separate departments, separate cubicles and they do not talk to each other often

Minnie – That’s True

Mickey – So they have very little contact and often do not know what is happening in each other’s life or work

Now whenever there was a deployment, there were issues like the code did not work on prod env or the env configuration was not as per the code, etc. etc.

Minnie – I see that every time there is a deployment

Mickey – With this there were a lot of trust issues between Tom and Jerry

Tom always said that he tested and the code works in Dev environment and Jerry said that the configuration of your env is different from production and many such things

Minnie – I can completely relate to this

Mickey – One day Tom saw Jerry in the company’s food court. He decided to approach and talk to her

Minnie – A turning point in the story!

Mickey – Tom offered coffee to Jerry to which Jerry hesitantly agreed

Minnie – huh! Attitude

Mickey – Slowly and gradually they started to talk and open up

Minnie – Now this is getting exciting

Mickey – While talking Jerry just mentioned that last production deployment failed due to some values in the configuration file that was as per dev env and stressed that it took her entire night to figure out and fix that

To this, Tom said, hey you could have called me, it was a few min job for me

Minnie – Really

Mickey – Yes, and similarly they talked on many such instances and issues in the past that could have easily resolved, if they collaborated in a better way

Minnie – Yes, I know that happens everywhere, even in personal life, You need to sit and talk and discuss calmly and resolve issues

Mickey – Can we come back to Tom and Jerry

Minnie – Yes!

Mickey – So after their long discussion Tom and Jerry decided to work together and collaborate with each other, share knowledge and responsibilities

Minnie – Nice twist in the story

Mickey – Yes, they became friends and met every day in the office food court and discussed work and issues. They started talking often and build very good communication

Minnie – Great

Mickey – They started to meet out of the office and spent a lot of time with each other

Minnie – A new beginning

Mickey – One day Tom said they could keep a separate configuration file for every environment and can save a lot of time and unnecessary issues. Jerry agreed happily

Another day Jerry suggested having the Dev env mimic Production configuration, which could help them to catch all possible deployment issues much earlier and Jerry could do that in minutes. To this Tom agreed happily

Minnie – I know where this is going

Mickey – Climax is yet to come. Wait and listen

Minnie – Okay, now I will keep quiet till the end

Mickey – So the friendship kept growing and very soon most of the Dev(coding) and Ops(deployment) issues became very less, The deployments were faster and efficient

Tom and Jerry started spending a lot of time together, discussing work, issues and thinking about more and better ways to make the software development and delivery process better, efficient and faster

One day over coffee, Tom suggested automating the testing of the code that will save a lot of time. Jerry agreed and suggested to have automated deployment after automation testing is a Pass

They then searched and found the right tools to automated the testing and deployment processes

Then they thought of processes and tools to automate other workflows and monitoring processes

This collaboration continued and Tom (Dev) and Jerry (Ops) kept working together and this resulted in the most efficient process of Software Delivery

Minnie – WOW

Mickey – So this is DevOps

Efficient collaboration between Dev and Ops to improve the quality, process, speed, accuracy, monitoring, and feedback process of software delivery

It is a process, not a tool or technology

It is a process of collaboration, communication, working together, automating and improving the processes in the life cycle of the Delivery Process

Minnie – I can see a Tom and Jerry in every organization

Mickey – Yes, This story is inspired by true lives and real events

Minnie – Everyone needs to know this story. I will share this with All

Mickey – Please do

Minnie – I will never forget this. You are my best friend Mickey and will always be

Mickey – I am always here for you 🙂


about the author more stories

227