Member-only story
DevOps Is Dead, Long Live NoOps
Learn why DevOps is not enough
Sorry for writing this clickbait title. I hate to use these tricks, but I needed to get your attention. In the IT trend, DevOps is the buzz word, nowadays. It happened some years ago with front end, when SPA (Single Page Application) became rampant.
I think it is usual in technology adoption. There is a moment when a new technology is breaking, adopted by enlightened people, becomes accessible to all, and spreads.
That happened to DevOps during the last few years. In the next few years, you will hear the new buzz word: NoOps.
What Is the Difference Between DevOps and NoOps?
DevOps is the fusion of development and operations and is the practice of development and operations engineers collaborating together to define processes that drive the service lifecycle, from the design to the delivery.
NoOps means no operation. Its philosophy is to remove all the platform management parts and reduce friction between developers and infrastructure.
Why Do We Need DevOps?
Technical and business requirements are more challenging and IT service becomes more and more complex. That’s why the delivery is so important and why we need to orchestrate the whole process.
With the cloud, we don’t need more sysadmin, but DevOps technical and business skills are in high demand. To implement DevOps and move into a place where the benefits flow, you need to think beyond technical delivery.
Why Didn’t We Have DevOps Before?
There are many answers to this question. You may say that it wasn’t necessary because scenarios were simpler or there wasn’t enough culture.
I can agree with these arguments, but I think the root cause is another. From my experience, the bigger issue was due to technology. The automation of delivery was hard to implement.
Most of the systems, ten years ago, didn’t have a one-step build or a well-defined workflow like git-flow by default. At that time, there weren’t any cheaper CI solutions, so what is hard to implement is not implemented.
