DevOps, AIOps, or NoOps? Is NoOps the death of DevOps?

DevOps, AIOps, or NoOps? Is NoOps the death of DevOps?

Context Setting

The rise of the DevOps in the Organization has revolutionize the software delivery landscape by focusing on the automation and bringing Ops part of the team to increase the accountability and speed up the time to the market.

With the progressive advent of emergent technologies, almost all the organizations are looking at taking DevOps journey to the next level by integrating AI and Analytics.

Mike Gualtieri of Forrester Research coined the term NoOps in his blog post “I don’t want DevOps. I want NoOps.” In the post, Gualtieri says, “NoOps means that application developers will never have to speak with an operations professional again.”

And, this debuted an entire world of NoOps.

So if you’re a DevOps professionals and NoOps scares you? Or you’re an optimistic DevOps professional and willing to take your career ahead?

Read this article and will answer all you queries.

A Brief history about Agile and DevOps

Agile movement started in 2001 in response of Waterfall with a vision to deliver a small and frequent values that matters to customers. But agile community was really struggling to deliver small and frequent values without having effective collaboration, communication and automation in place.

Here are few references, Agile Is Dead, Long Live Continuous Delivery, Is Release Management Dead? And The Death of Agile and Beyond

And rise of DevOps in 2009 has really revolutionary entire Agile movement by integrating DevOps principle. And, world has witnessed the software delivery frequent cycle.

Now with the advent of Artificial Intelligent and promising future for Ops in it, Industry started debated “What is next of DevOps”

What is AIOps?

The Artificial intelligence for IT Operation is called AIOps. AIOps is the NextGen and future of IT Operation. AIOps integrates advance algorithms and AI for analyzing the raw data from the numerous sources and provide meaningful information to speed service delivery, increase IT efficiency and deliver an exceptional user experience.

Going forward, AIOps will play a key role in enabling new efficiency for IT Ops teams. It will also make practical the adoption of complex next-generation technologies that cannot be managed successfully using tradition solutions.

Key drivers for AIOps

With massive growth of AI and wider adoption of Digital Economy, the traditional IT management techniques are becoming obsolete to manage increasing complexity and responding to the changes spontaneously.

  • AIOps addresses the challenges of speed, scale and complexity that todays’ leaders are facing. Here are the main key drivers for AIOps adoption.
  • Data Analysis and quick decisions – Today’s IT infrastructure and APM landscape generates massive amount of data that human can’t parse and derive meaningful insights. Here AIOps can be used to consume the data, develop intelligence around and provide meaningful information around it.
  • Faster Response Time – Growing the complexity of the enterprise tools landscape and massive data increases the volumes of alarms and services tickets. Manually it’s very difficult to keep eyes on all the incoming and respond fast.
  • Predictive Maintenance – Proactively predicting the issue and acting before it hits the service delivery is the key priority for any service delivery to deliver exceptional user experience. And, AIOps can play a vital role by leveraging its machine learning and advance analytics.
  • Enable the culture of self-service – With intelligent automation and right real-time information at hand, AIOps foster the culture of do it yourself. Its holds the owner of code, infrastructure and support team accountable for delivering the services faster, cheaper and better. 

Use Cases

Proactive Bottleneck Identification – AIOps can be used to predict the serious bottleneck and avoid the service disruption by leveraging huge data and analytics.

  • Self-Healing – AIOps can be used to avoid service disruption by remediating issues automatically without any manual intervention. Self-healing is a very powerful feature of AIOps and can be used to solve complex IT operations like performance, monitoring, configuration by proactively detecting the problems and remediating before its impact the services.
  • Root Cause Analysis – AIOps can be used to analyze log files, help desk emails, incident management tools and incident logs to analyze the root cause of the problem and find the relevant remediation. This is really complex problem to be analyze and reach to a conclusion by the human.
  • Alarm Monitoring – With growing IT complexity and increasing devices with the realm of the connected world, it’s very difficult for human to monitor the alarms and deliver services at the expected speed. Hence, AIOps can be used to monitor the real time alarms raised by different devices (servers, firewalls), analyze the nature of the problem, engage the right team, and if require remediate the issue without any manual intervention. 
  • Intelligent Automation – AIOps can help the IT Operation team to become more productive by leveraging RPA bots and Chatbots. RPA can be used to automate repetitive, mundane and highly transactional activities, wherein, ChatBots can enable human like conversation and bridge communication gap.

Where AIOps does fits into IT Environment?

Looking at AIOps, and hearing integration of complex algorithms and advance analytics with IT, confuses and creates curiosity how this will fit into overall modern IT tools landscape? Really it will replace the existing monitoring, log management, service desk, orchestration tools and entire support staff?

The answer is NO.

The objective of AIOps is not to replace the existing IT tool landscape, but rather complement and sits on the top of the existing infrastructure to consume the data and provide useful real-time information to its users. The objective is to empower ITOps to drive business for the 21st century by leveraging cutting edging technology.

Is it DevOps dying? Are we relevant in our job?

DevOps isn’t dying. It is evolving.

The objective of AIOps / NoOps is not to replace the existing IT tool landscape, but rather complement and sits on the top of the existing infrastructure to consume the data and provide useful real-time information to its users. The objective is to empower ITOps to drive business for the 21st century by leveraging cutting edging technology.

Despite of the cries of the DevOps death, NoOps is not the end of DevOps. In fact, NoOps is only the beginning of the innovation where we may achieve integrating DevOps and Intelligent Technologies.

What in it for you?

If you’re a DevOps Coach/Agile Coach / PM or aspiring Agile Geek and curios to know

  • “WHAT IS NEXT AFTER AGILE AND DEVEOPS MOVEMENT”?
  • How to create micro niche in Project Management?
  • How to become highly paid Project Management Professional in year 2020?

Please permit me to express my experience. Intelligent Automation is the next movement in the age of digital disruption. And, only Project Managers will thrive and survive, who are ready to embrace and adapt Intelligent Automation along with Project Management skills.

How to move forward?

If you’re excited and action takers, I’m right here to help you.

Join my Facebook group –  Digital Project Manager

Follow my upcoming webinars –

Follow my Blogs – Blogs

Rameshwar Balanagu

Growth Focused IT Executive & Digital Transformation Leader | Driving Business Growth through Innovative Tech Strategies | Connecting Vedas 2 AI for a better& brighter civilization | Startup Advisor

5 年

very well written and extremely beneficial. I personally do not like the word Noops . Perhaps it should be Allops or Digitalops? or whatever is the? buzz word . we need to stress the fact on devsecops? and Bizdevsecops as well. Noops or Allops or XYZops needs a pipeline from Biz to security .?? Amidst the hype of everything ,IT4IT has done a great job of?creating 4 value streams and connecting all ops together? with the teams included . Please have a look at it as well

回复
Smita Kelkar

Digital and Transformation R&D Leader (Lean Agile) | DevOps Evangelist | QA-QC-QM-Automation Expert | Passionate Coach & Mentor | Innovation Propeller | AI Enthusiast | Ex - Siemens | Ex Ensim | Motto - Meet n Benefit

5 年

None will substitute each other . I feel these are sequenced phases. For an org with complete legacy , smart automation leading to Devops is the trigger . Next steps could be making it lean and identify three directions - 1.Take predictable steps to AIOPS 2.Plan classified and predictable to SmartOps leading to NoOps 3. Work hard to identify and put nonautomated ones to DevOps ( take UiPath as one of the tool to rescue) . This has to be more inclusive move across the org. At DevOps and AIOps - leverage strengh of experts At NoOps - use your PM and Operations management key personnels' skills Nothing dies because if organization identifies the need of the hour correctly and act accordingly.

要查看或添加评论,请登录

Madan Upadhyay的更多文章

社区洞察

其他会员也浏览了