- DevOps originally was supposed to eliminate Operations (Sysadmin) staff by involving Dev with the Infra and Release process. - But Dev is incentivized to create features, not know the intricacies of Release at scale, so dedicated Devops (Operations) teams were again staffed - dedicated DevOps teams are here to stay except in certain unique scenarios. For example, I've seen some Indian-led SV startups that hate Oper…
DevOps is dead. But what will replace it?
21–30 of 64 posts
Re: DevOps is dead. But what will replace it?
#22No full author name in the article, nonsense article.
Lack of a name means absolutely nothing IMO.
Re: DevOps is dead. But what will replace it?
#23Could anybody explain what's the point of using 50% gray for main text font? Does it really look good to somebody besides the designer?
Re: DevOps is dead. But what will replace it?
#24Post misses the point of DevOps--there aren't DevOps engineers, there are engineers that do their own devops.
Re: DevOps is dead. But what will replace it?
#25> [...] DevOps is dead; the amount of DevOps engineers [...] Post misses the point of DevOps--there aren't DevOps engineers, there are engineers that do their own devops.
Re: DevOps is dead. But what will replace it?
#26Re: DevOps is dead. But what will replace it?
#27Re: DevOps is dead. But what will replace it?
#28Re: DevOps is dead. But what will replace it?
#29Its a very poorly written article with all the buzzwords one can think of. DevOps is not even remotely close to dead, but rather evolved a lot. Gone are the days, when one could easily ssh into remote prod systems and fix the issue. With shell less Docker images and container orchestration tools (hashicorp stack), CI/CD pipelines, blue-green deployments etc, Devops has become a lot more sophisticated than before.
I think we finally realized that fixing something in prod via ssh is not a good solution and might introduce new bugs on its own. Rather build an infrastructure that allows you to rollback fast. It is also not worth to fix individual machines in a big cluster, just throw them away and bootstrap them from zero. This way you make sure that you don't have accumulated patches and workarounds on your nodes that might lead to future failures. In some companies we reached the point where you don't even fix a cluster in a multi-cluster setup, but throw away the whole damn thing and bootstrap it from zero.
Re: DevOps is dead. But what will replace it?
#30Its a very poorly written article with all the buzzwords one can think of. DevOps is not even remotely close to dead, but rather evolved a lot. Gone are the days, when one could easily ssh into remote prod systems and fix the issue. With shell less Docker images and container orchestration tools (hashicorp stack), CI/CD pipelines, blue-green deployments etc, Devops has become a lot more sophisticated than before.