DevOps — Making the marriage work
by Anupam Kulkarni, Co-Founder, iauro
DevOps is the present as well as the future, and a lot’s riding on the way organizations are leveraging it. While it all sounds hunky-dory, the threat of it going wrong looms over our heads constantly. The problem does not lie in the way it’s conceived but the way it’s being perceived. In fact, DevOps is pretty much like an arranged marriage. An alliance brought about by well-meaning people who have evaluated various aspects including compatibility. There is the inherent need and desire to make it work, while eliminating unnecessary hiccups along the way. In my opinion, there are things we need to stop right away to ensure that the honeymoon never really stops for DevOps. Here’s a quick look at things that need to be addressed right away if we want it to give us the edge and support we badly need today.
The divide still exists
While the whole point of having DevOps was to bring together and create a collaboration between development and operations teams, they continue to be at war in some environments. The communication continues to pose a challenge. Silos exist, so do concerns pertaining to security, performance and business metrics. DevOps can bring a whole new perspective to teams and organizations provided we look at it as a means to ease out the discord, and not treat it as some kind of one-stop solution. Just like husband and wife, the teams working on DevOps have to consciously work towards ironing out friction and set sail for the journey ahead. It’s a marriage of families and a few but significant adjustments need to be made. Also, the right tools and processes need to be incorporated to bring about a conducive change in culture and process. All this takes time, and return on investment will not be visible immediately.
Rigid way of functioning
No doubt DevOps comes with a set of rules, but they are only meant to make you more agile as an organization. They cannot pose as a hindrance and if the situation warrants, you need to go ahead and tweak them a bit to allow for greater flexibility. Just don’t make it a habit, and use discretion when working around these rules. The focus should largely be on speed-to-market while keeping a close tab on delivery commitments and your business goals.
A myopic approach towards administration costs
The whole purpose of having DevOps gets refuted when you unnecessarily tighten your grip on the administration costs. A lot of organizations are unable to let go of the past also because they have heavily invested in old tools and processes with respect to time and money. DevOps may be expensive initially but it does go a long way in eventually improving the efficiency and the financial well-being of the company. While a lot is being done to bring down the administration time, the admin costs continue to remain a concern for many. Asynchronous vendor update challenges, extensive plug-in architectures, and the perennially increasing requirements keep teams way too busy to examine and assess the ecosystems for loopholes. The good news is that we do have systems and tools in place to address them and efforts are being made to enjoy continuous support from rapidly evolving environments.
DevOps does have a bright future and the marriage can definitely weather the many ups and downs if there is solid support. This could come from an expert who understands DevOps like the back of his hand and can streamline solutions as per your needs. Just the way a Patriarch would. Once you have the necessary support, you can safely assume that Dev and Ops would continue to live happily ever after…