Question

You might have recently heard the term “DevOps” being tossed around. I've read a wiki and didn't fully understand what this term means: "Companies with very frequent releases may require a DevOps awareness or orientation."

Can you give a real example to understand what it's like?

Was it helpful?

Solution

In a very simple explanation

- Dev---> to Operation

You will need to automate the deployment for frequently build, batches, hot-fixes or SPs.

- Operation----> to Dev

You will need to automate and streamline the incident management, the support tickets and the debuging with the dev teams

OTHER TIPS

As per traditional IT process-

DEV | Ops

Imagine the vertical line as a silo between the Development Team and the Operations Team.

To deploy new applications or to deploy enhancements to a current running one developers used to volley their codes over this wall to the court of Operation's team. So collaboration between Dev and Ops was minimal which resulted in issues viz. " Work in test but why the heck its not working in production environment".

This led to frustrations, reinventing the wheel on various counts, multiple reviews, delays in timelines which eventually impacted the ROIs

Hence

To negate the above mentioned issues the need of the hour was to bring in a process which infuses a sense of collaboration, innovates to inculcate automation at various stages wherever feasible.

So the silo was broken down resulting in

DEV-------------->>> is moving towards OPS

&

OPS-------------->>>>>is moving towards DEV

Hence the evolution of "DEVOPS"

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top