Live data from Hacker News

DevOps is dead. But what will replace it?

edgegap.com

51–60 of 64 posts

Re: DevOps is dead. But what will replace it?

#51
post #45

Earlier quoted context omitted.

I’ve never really gotten this argument. People can go really deep on Terraform, Cloud Automation, CI/CD, containerisation etc without being developers or sysadmins. “DevOps Engineer” fits that role perfectly in spite of the breaking-down-siloes goodness.

The DevOps tool chain has become so complex that it requires specialist roles that create knowledge silos. The goal of DevOps was to remove those gates and silos. It was meant to be about skills over roles. All we appear to have done is change the tools and role from that of a SysAdmin to DevOps engineer.

Then you're doing it wrong. My teams have two components that require review from a specific group:

1. Core infra

2. Anything related to security

Outside of those, we all can and do work on everything else. We regularly coach people in terraform and third party APIs to endure they understand that they own their application lifecycle. They control the entire SDLC and we work together to ensure sanity. There are lots of bumps but nobody gets a pass on understanding the in and outs of software development and management. I can't see a cloud based offering being successful without that.

Re: DevOps is dead. But what will replace it?

#52

- 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…

> in larger companies, Devs don't have access to production, so again dedicated DevOps teams are needed if only to enforce policy

Nor should developers be let near productions as they'll always try to root cause problems in production. Developers are their own worst enemies which is why DevOps is a misnomer.

Re: DevOps is dead. But what will replace it?

#53
post #45

Earlier quoted context omitted.

The DevOps tool chain has become so complex that it requires specialist roles that create knowledge silos. The goal of DevOps was to remove those gates and silos. It was meant to be about skills over roles. All we appear to have done is change the tools and role from that of a SysAdmin to DevOps engineer.

Then you're doing it wrong. My teams have two components that require review from a specific group: 1. Core infra 2. Anything related to security Outside of those, we all can and do work on everything else. We regularly coach people in terraform and third party APIs to endure they understand that they own their application lifecycle. They control the entire SDLC and we work together to ensure sanity. There are lots o…

[deleted]

Re: DevOps is dead. But what will replace it?

#54
post #45

Earlier quoted context omitted.

The DevOps tool chain has become so complex that it requires specialist roles that create knowledge silos. The goal of DevOps was to remove those gates and silos. It was meant to be about skills over roles. All we appear to have done is change the tools and role from that of a SysAdmin to DevOps engineer.

Then you're doing it wrong. My teams have two components that require review from a specific group: 1. Core infra 2. Anything related to security Outside of those, we all can and do work on everything else. We regularly coach people in terraform and third party APIs to endure they understand that they own their application lifecycle. They control the entire SDLC and we work together to ensure sanity. There are lots o…

So you have a DevOps team?

Who is doing what wrong, according to whom?

Re: DevOps is dead. But what will replace it?

#55

- 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 originally was supposed to eliminate Operations (Sysadmin) staff

It wasn't. It was supposed to break down the model of Dev and Ops being separate silos that don't work together well and don't understand/respect each others concerns.

Re: DevOps is dead. But what will replace it?

#56
post #32
post #14

This is a garbage quality post but the underlying premise I think is fair. I’ve heard much more reputable people like Kelsey Hightower make similar claims recently. Just as a matter of personal interest I spent the last year looking into the question of how close could a small and possibly even competent one person team get to doing “cloud native” “best practices” from day one if they made the right choices. My asses…

> Running Kubernetes for example has in just the past couple of months potentially become a genuinely hands off exercise thanks to GKE Autopilot where you can just throw containers at it and it will just work and do the right thing by default. I never heard of Autopilot before but it sounds like what AWS has had for a while with Fargate where you don't need to manage your worker nodes, instead you define what compute…

>Things like this are definitely a very welcome change but running a production workload on Kubernetes is still no where near a hands off exercise, even with the cluster creation and scaling aspect abstracted away. There's still learning, using and applying Kubernetes.

I think that's what this article alludes to. You won't need to manage Kubernetes with an automated container orchestration platform that just needs your container or cluster. If an automated system can take care of the management, then the "cloud management" part of DevOps is greatly reduced.

Re: DevOps is dead. But what will replace it?

#57
post #36

Here we go again. The view in this article is that DevOps is a role, it was never meant to be this way. The whole purpose of DevOps was to break down barriers between Dev and Ops, by not creating specialist roles and allowing developers to take ownership of ops, removing the need for the SysAdmin gates. Instead what this article highlights is that we’ve moved the complexity to specialist tools which require another s…

I think you're mixing theory with practice; DevOps should not be a role, but it often is...

As for requiring another specialist role, that's not the goal of building an automated system. Or at least, this specialist will not part of the team that's building the product, but rather of the company that's building this automated platform. If you can automate the orchestration and management of Kubernetes or serverless, then developers just need to know how to build a container or upload code on a serverless platform.

Re: DevOps is dead. But what will replace it?

#58
post #3

This post doesn't really say anything and hand waves over a lot of the complexities of real world deployment and operations that isn't a simple stateless hello world web application.

I don't think the point of the article was to say technically how to automate everything. But rather that the tools to automate are coming and that we should be on the lookout and ready when they come.

Re: DevOps is dead. But what will replace it?

#60
post #26

Its 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.

You say sophisticated but in reality, it has become extreamly complex, which is a natural consequence of using tons of different tools and glueing them together.

And that's why there's room for automation to take a lot of the complexity away.

Granted it's not going to be easy to have a platform where every tool can seamlessly connect, but we can start with baby steps such as services that automate multi-cloud deployments like the article suggests.

Post reply on HN