Dissecting The Role Of DevOps In Contemporary ERA

By Kavita Viswanath, General Manager – India, JFrog

Kavita Viswanath, General Manager – India, JFrogKavita has over 19 years of experience in leading Enterprise Sales, Alliances, Strategy, and Planning for core technology as well as e-commerce companies. As the General Manager with JFrog in India, she manages business and operations including R&D, support, sales, marketing and finance.

DevOps was started as a method of bringing developers and operations together. It is not an operational strategy, rather a methodology that many companies have started adopting. Methodologies have now come to a level where there are a plethora of tools available in the market to support it, making it easier for organizations to undertake operations. Traditional methodologies included changing the culture, team structure, and aligning them to figure out how to bring the DevOps concept together. However, this methodology has matured quite an extent across the globe and organizations have started thinking of DevOps right from the beginning of their product design. The concept has been ingrained into the whole development and product design of the organization to signalize the need to deliver products and upgrades faster. Today, DevOps has been widely adopted across organizations despite the geography and the vertical they belong.

“Being reluctant towards DevOps would not be a smart move for companies since software could be a target of vulnerabilities and security issues in the future”

The Trigger that Drives the Change

Almost a decade ago, Cloud was fairly a new concept that only developed nations commenced on. Technologies, or software, were still being used in a three-tier architecture model. However, in today’s Cloud world, there are multiple concepts floating around such as Hybrid and Native Cloud. These concepts have made software extremely complex in nature. Organizations embark on micro services in IoT and containers, which play a huge role in the way software is designed and delivered to end-users. The end-users may not be aware of it, but there is a whole web of complex delivery of software in which the reason that triggered the need of DevOps has awakened. This evolution from a three-tier simple architecture to a complex multi-tier model of delivery or designing of software is led by the demand arising from users. In the smartphone era, users expect updates for the product or software practically on a daily basis. This is how users' adoption of software has changed or the way it has impacted their lives. Therefore, organizations have immense pressure over the need to design software that keeps the user connected, while adding novel features and security updates on an uninterrupted basis. This factor has stimulated the evolution of DevOps when organizations identified the need to deliver software, which is far more complex in nature that requires updates.

Alterations in the Organizational Structure

The first big change should start from the executive levels. DevOps practices need to be blueprinted from the senior level of the tech leadership, including CTOs and CIOs. We cannot think of DevOps as a broad stage to deploy software in the production environment and operationalize the core once it is built. This is the big change that organizations need to start thinking about and we have already seen the change with the customer with whom we interact. At a blueprint stage, when you think of how the quality team, the testing team, and security team need to work together as a single unit, this is where the DevOps practices and adoption take form and shape. Here again, we can perceive the aberration from its traditional practices. Today, most of the companies have a DevOps team which is a part of the CTO team. It is no longer a tools team or an operational team that is placed elsewhere within the tech organization. While you observe the legacy product companies, it takes time for them to change the team structure overnight. Legacy organizations adopt these alterations by exercising at a unit level or in phases. When changes are made in the team structure, DevOps practices are more ventured and formulated to orchestrate the team work as well as automate at different phases. Once they become confident in that practice, then it can be deployed from premiere to the core or legacy teams, bringing slow changes.

Automation is the Future

In 2018, the DevOps market was pegged at USD 6.5 billion globally. In early 2019, Gartner and Forrester forecasted the DevOps market at USD 12.5 billion for over the next five-year period. Having observed the addressable market potential doubling year over year, it is evident that more companies are adopting DevOps practices. The trend will be catching up big time in the next decade or at least within the next three to five years’ time frame. In India, the field has tremendous opportunities since it has got the right mix of development houses. We have 18+ unicorn tech companies in India spread across ecommerce and fintech sectors. Being reluctant towards DevOps would not be a smart move for companies since software could be a target of vulnerabilities and security issues in the future. It is about figuring out how near or far away you are in the DevOps curve in terms of automating the processes and the overall core to deployment pipeline. I think that is where the focus and the innovation will descend in the near future. Automation is no longer a choice but a necessity. It is something that is easily available in terms of the tools for the development of an organization. Eventually, everything depends on how smartly one uses the automation in their day-to-day life – developing the core towards deploying it.

Don't Miss ( 1-5 of 25 )