DevOps: What's All the Hype Really About?


Published on

Why is DevOps quickly becoming a popular role that businesses seek to fill?

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

DevOps: What's All the Hype Really About?

  1. 1. DevOps: What’s All the Hype ReallyAbout?DevOps is a concept that has materialized fairly recently, yet is already adored by somany people. Obviously, the fact that it bridges the chasm between softwaredevelopment and operations is pretty exciting, but there seems to be something extrathat people love. So without throwing around too many corporate buzzwords (besides“DevOps”, of course), what could that extra something something be?SpeedOne of the allures of DevOps is its ability to speed up the back-and-forth between Devsand Ops. By helping developers and system operators work together, it leads the twodepartments to clearer and more transparent interaction, breaking down the siloshousing Devs and Ops. This increase of speed is not limited to the interactions betweenboth of these groups – it also gives companies the ability to continuously deploy newiterations (i.e. multiple times per day) of their infrastructure, as opposed to rolling outrelatively large deployments over a vastly longer period.Stability
  2. 2. Because of its nature, which encourages collaboration, DevOps leads to greater stability.Because of this collaboration, there are more eyes on every deployment, meaning thatthere’s also a greater chance of someone seeing a potential serious flaw before arelease occurs – DevOps, in practice, basically creates a safety net. DevOps can alsolead to stronger appsecurity. Increased security is related to the fact that DevOps leadsto shorter time between releases; the complexity of the coding is reduced because ofoverall smaller, more frequent deployments.CultureThe concept of DevOps doesn’t simply offer a solution to a problem; it also has thepotential to create a positive change in a company’s culture. Creating synchronizationand strong communication between Devs and Ops can be paramount in getting rid ofsome of the headaches that come with changing a company’s infrastructure. This canmake everyone happier and easier to work with, especially given how difficult it can befor developers and system operators to work together at times.Put simply, DevOps has the potential to create peace between developers and systemoperators.DevOps Still Has Room to GrowDevOps is far from complete. The “synergy” (sorry, I had to throw in at least one otherbuzzword ☺) that DevOps creates between developers and system operators can beexpanded to other departments, like marketing or sales. Essentially, if everyone in acompany can be on the same page, regardless of what business function they support,the company’s efficiency will be significantly improved.Great, So Everyone LOVES DevOps Right?There are plenty of people who see DevOps as more of an abstract idea, or as anarbitrary title, than a true business function. A strong reason for this is probably due tothe fact that implementing a “DevOps culture” is easier said than done. Just because acompany says: “okay, we want our developers and system administrators to worktogether, let’s hire a DevOps person”, doesn’t mean they have any idea just how to findan effective one, or even what specific role this person should play.
  3. 3. Another argument against DevOps comes from the fact that developers and sysadmins’workflows could be potentially thrown off by someone becoming more involved inmanaging exactly how deployments are implemented. For example, a comment Irecently encountered from a developer on why they find little value in DevOps cited theirdesire to code at their own pace being potentially ruined by meeting an “agile”deployment cycle.Hmmm, So is DevOps Worth Pushing in My Organization?Obviously, this argument will have different answers depending on the companyconsidering using DevOps. It seems DevOps is generally a good idea for a companythat:- Has a rift in communication and execution between its developers and systemoperators- Needs to implement more frequent and less complex deployments- Has a lot to lose as a result of poorly implemented deployments- Knows what DevOps is, and that has a clear understanding of HOW they plan tointegrate a DevOps culture