The Ops Perspective 2017: NoOps Through the Eyes of a DevOps Engineer

What is NoOps for a DevOps guy? If you ask a coder, he/she will be whip-smart enough to tell it is something about ‘No Operations.’ And if you ask a DevOps engineer, you would have evoked several emotions in him/her. Few say it’s automating everything underlying the infrastructure, and few counter argue saying not everything can be automated; NoOps just involves stuff that minimizes few steps in the IT operations. Whatever the case, few experts say, NoOps is a progression of DevOps.

What NoOps means to the IT industry:

Several research companies, who have been following several IT Cos fro decades, have come up with their own version of NoOps definition. Tech Target defines NoOps as a concept where an IT environment can become so automated and abstracted from the underlying infrastructure that there is no need for a dedicated team to manage software in-house. Which means: No dedicated team will be required for operations while the application development team can itself manage operations.

On the other hand, Forrester defines NoOps as “the goal of completely automating the deployment, monitoring and management of applications and the infrastructure on which they run.”

Adrian Cockcroft from Netflix, in one of his blogs, mentioned that the Platform-as-a-Service (PaaS) will produce lesser needs for operations which in turn gives rise to NoOps culture.

So many versions, and so many ideas, out there. Phew!

So, what does NoOps mean to the DevOps fraternity? Why do experts predict that NoOps is a progression of DevOps?

Read the full article on our blog HERE.

What is your take on this? Do share your thoughts below in the comment section, or on any of our social media pages Twitter, Facebook or LinkedIn. Do read the Botmetric blog post on Alert Analytics to see how Botmetric is driving cloud management with NoOps capabilities.
One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.