DevOps is not something you buy in a box – it’s about cultural change

Send to friend

DevOps is a cultural change that encompasses people, processes and technology tools to focus on the rapid delivery of business solutions and applications. This is according to Kelly Murphy, Co-Founder of HyperGrid, the Enterprise Cloud-as-a-Service leader.

"First and foremost, DevOps is about culture; and its purpose is to develop and deliver business applications and drive faster time to value for a business. DevOps culture is about the collaboration that takes place across the different groups in an organisation, leveraging different tools and different processes to accelerate this innovation. The output of DevOps is a continuous application delivery that evolves quickly to figure out what works best for the customer while using our applications," stated Murphy.

"It's about driving continuous innovation for the business and its customers. For example, traditional enterprises typically deploy an application once every 12-18 months with maybe six-month updates. Web-scale companies, on the other hand, deploy applications many times a minute. The difference between these two is really the scale of what's being deployed," he added.

In a Gartner survey, 75% of enterprises saw significantly faster delivery times and more importantly, time to business value. According to the same research from Gartner, 38% of enterprises already have production systems or production pilots underway - with a further 35% of enterprises planning to implement a DevOps process in 2017.

The tooling of DevOps leverages containers and micro-services to break an application down into small, granular chunks of code that operate in containers that are loosely coupled together. Each of these micro-services is automatically deployed in a container and can be easily updated many times a day through a continuous improvement, deployment cycle, leveraging the feedback that comes from its end users.

"This process of development is also interconnected with operations through the container technology and deployment automation of these containers. Within the container, the developers define the exact infrastructure they require which is automatically delivered. Everything in this process is controlled, governed, monitored and fed back to the DevOps process for further improvement," continued Kelly.

The result is a process that rapidly can zero in on what works best for end users while eliminating quality or infrastructure issues before they become a problem.

Comments (0)

Add a Comment

This thread has been closed from taking new comments.