|
|
|
|
|
|
by ai_ja_nai
3244 days ago
|
|
|
While a completely stateless and auto scalable infrastructure is desirable even by Ops people themselves, reality doesn’t always allow for this because:
Not everything can be event driven.
Persistent data will always have to be managed by somebody. Plus, NoOps conceals the risk to have a de-evolutions of devs into even dumber IDE users that can’t even type “sudo systemctl start mysql” at the terminal. NoOps as a company wide phylosophy can’t be tenable. |
|
|
You can say the same thing about ops people being "dumb command line users who can't debug assembly language."
Higher abstractions and fewer reinvented wheels are one of the major overarching goals of computing. If I never had to type "sudo systemctl" ever again for anything but a fun antique restoration project then I would be very happy.
That said, I completely agree that for any company other than maybe some early-stage startups to go completely NoOps today, in 2017, is not a good idea.