Just remember that NoOps isn't actually no operations. That's the cargo cult version of NoOps. Instead it's outsourcing operations and relying that the outsourc

Just remember that NoOps isn't actually no operations. That's the cargo cult version of NoOps. Instead it's outsourcing operations and relying that the outsource vendors operations team will do a better and more accountable job than any internal team you could build. So, a database service instead of a locally managed database and a reliance on the service vendor to back things up, keep the code up to date and manage reliability. That's not a bad choice but you still want someone with the judgement to evaluate vendor claims, performance, exceptions and the like.