NoOps is here, and it’s great

This has to be a touchy subject, right? Somewhere out there is a “DevOps is dead, long live DevOps” blog post, and an accompanying Reddit thread that reads like an Anchorman-style newscaster brawl. Which, by the way, isn’t a bad thing. However, the boring truth is DevOps and NoOps solve the same problem, but in different environments.

NoOps didn’t simply appear out of thin air as a result of wishful thinking, and no, it wasn’t as if millions of ops voices suddenly cried out in terror and were suddently silenced.

NoOps needed the right environment. It needed PaaS, microservices and serverless.

I’ve built and deployed my fair share of monolithic web applications. They run on clusters of app servers, and the deployment process becomes increasingly complex and brittle over time. It’s hard to imagine anyone NoOping one into PROD, let alone the underlying app server cluster and the infrastructure it runs on. This is a problem for the DevOps team.

But if we’re talking about microservices, it’s a whole other story. There’s no app server, no cluster. We just need a runtime. Somewhere. Anywhere. It doesn’t matter.

The only thing we need to run and scale our microservice is the ability to deploy multiple copies of it and its runtime. Enter Amazon Fargate and other serverless infrastructure.

This is a problem for… the PaaS. It can build our microservice from source, containerize it and deploy the container to serverless infrastructure with automatic scaling.

I mean, It’s not exactly NoOps if you have to build and deploy containers yourself.

It’s really about the abstractions PaaS, microservices and serverless provide. The higher the abstraction, the smaller the need for manual ops.

More on that in our next post.

Get great content updates from our team to your inbox.

Join 86,000 subscribers. GDPR and CCPA compliant.