The Perspective: 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; it 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 it 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!
What NoOps means to the DevOps fraternity:
For many, who take the literal meaning of it, perceive that with NoOps there shall be no operations whatsoever and that a system will start, manage, report and repair resources in IT infrastructure by itself.
And for a hard-core DevOps engineer “NoOps is a progression of DevOps.” For this engineer, it is just a process that minimizes Ops tasks by 10-15% and thus helps free-up a developer’s time for more innovation.
In other words (or from the eyes of a DevOps engineer), NoOps means performing DevOps with lesser Ops involvement. And that some parts of processes of DevOps will still be used for it. So, both are no much different. This is why, it is seen as a progression of DevOps. Similar to how DevOps was a progression from IT Ops.
Lucas Carlson, CEO of Appfrog, once said, “SysOps is blu-ray but NoOps is streaming. Blu-ray is going to be around for a long time and there is a strong market for it. There will be people wanting to play Blu-ray disks for decades to come. But streaming is a generational shift.”
The last word: NoOps is a progression of DevOps
The ultimate vision of NoOps is to free-up developers’ time to further utilize their time for more innovation. Whatever you perceive it is: zero Ops, Ops controlled by bots, eliminating Ops workforce, Artificial Intelligence (AI) Ops, or more, it is a rolling stone with the right momentum.
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.
Latest posts by Editor (see all)
- Top 5 Reasons Why AWS for Fintech is a Perfect Match - March 30, 2017
- DevSecOps: A Game Plan for Continuous Security and Compliance for your Cloud - March 27, 2017
- The Road to Perfect AWS Reserved Instance Planning & Management in a Nutshell - March 17, 2017