By Originally Published On AppFog
Since having our infographic published on GigaOm, there has been a lot of controversy and FUD around “NoOps”. Paul Graham recently wrote about schlep blindness. NoOps is a response to the schlep blindness of developers doing SysOps.
What does NoOps mean?
- NoOps means developers can code and let a service deploy, manage and scale their code
- NoOps means automated systems like CloudFoundry managing app lifecycles, not SAs “the point isn’t that ops are going away, but they’re going away for developers” – Derrick Harris at GigaOm
What does NoOps NOT mean?
- NoOps doesn’t mean that operations are dead and nobody will do them (like this tweet thinks)
- NoOps isn’t a job role (like this tweet and this tweet thinks)
- NoOps isn’t blissful ignorance (like this tweet thinks)
- NoOps isn’t marketing fluff made up by non-technical idiots (like this tweet and this tweet thinks)
This is the true spirit of NoOps:
“Netflix runs NoOps … Netflix is a much larger example of a PaaS based NoNops organization … We claim a competitive advantage from the agility and automation of a PaaS based product and a NoOps organization.” – Adrian Cockcroft, Cloud Architect at Netflix (read more)
The growth of the SysOps movement has been driven mainly by developers who were tired of...