NoOps! Is that even a term?
The world is moving swiftly. Especially in the IT industry where technology keeps changing at a lightning speed. We have moved from Servers to containers, datacenter to cloud and monolithic to micro services architectures.
With the fast evolving IT industry, IT teams too are evolving themselves. From IT Operations (ITOPS) to System Operations to DevOps. But then what next?
The way IT teams have evolved from traditional ITOPS to DevOps, you can see it is directly proportional to the change in infrastructure as an offering. With everything as a service model, be it compute, network or storage it becomes easier to automate and maintain infrastructure.
Someone who has been in the IT industry must be surely aware of the old days when IT teams who typically used to be involved in more of hardware related activities like datacenter management which included networking devices , bare-metal servers, computers ,help desk, and so on.
Then came a phase where teams of system administrators and network administrator who along with typical IT operations, would also automate few of their mundane activities like application backups, disk clean ups and scheduling cronjobs.
As the evolution continued, and as they say “Alone we can do so little; together we can do so much” collaboration between Development and Operations teams gave birth to new group of resources called DevOps. DevOps tries to achieve an agile methodology with highest possible automation in the existing environment where no development and operations teams are working in silos. DevOps brings the cultural philosophy, practices and tools together to achieve a number of benefits like Speed, reliability, rapid delivery, scalability, security and many more.
The sole purpose of DevOps is to automate the process that are traditionally manual and slow.
Let’s consider a hypothetical situation where your DevOps team is able to achieve a full automation or automation to an extent where you ‘No more’ need operations team to perform any manual tasks or to manage infrastructure. This point of complete automation is called NoOps. It can be defined as “A goal of completely automating the deployment, monitoring and management of applications and the infrastructure on which they run.”
NoOps means that application developers will never have to speak with an operations professional again.
Before we target NoOps model it is best to work on creating a LowOps environment. LowOps is the first step in achieving NoOps model. LowOps is rather a practical situation which can be achieved.
NoOps still sounds relatively difficult to achieve and still is a concept than being practical case. But the speed at which the IT industry is making progress, one cannot deny the fact that NoOps is around the corners. A few examples of NoOps platforms are Heroku, Amazon Lambda, and Google Firebase. By adopting these platforms, you are practically achieving infinite scale.
With more and more SaaS based model being preferred, the possibilities for NoOps is growing.