Re:Ask HN: Is a “no-ops” architecture viable?
by gregjor on Wednesday July 03, 2019 @04:29PM
(#20348420)
No-ops means someone else does the ops/system admin. Depending on requirements you may find a fully-automated or turnkey setup. I can deploy a WordPress site on Digital Ocean (and other platforms) with a few clicks.
When something goes wrong you need ops support. Too many things can go wrong, I think impossible to anticipate all of them. The less familiar you (or whomever does system admin for you) is with the setup and environment the longer it will take to find and fix problems. The more complex the infrastructure (and serverless/microservices gets complex fast) the more expertise you need to deal with the inevitable problems.
When something goes wrong you need ops support. Too many things can go wrong, I think impossible to anticipate all of them. The less familiar you (or whomever does system admin for you) is with the setup and environment the longer it will take to find and fix problems. The more complex the infrastructure (and serverless/microservices gets complex fast) the more expertise you need to deal with the inevitable problems.