Live data from Hacker News

A Eulogy for DevOps

matduggan.com

1–10 of 175 posts

Re: A Eulogy for DevOps

#3

Am I correct in understanding that microservices and DevOps are closely related - in that microservices trade code base complexity for operations complexity?

You still have challenges supporting monoliths in production. I don’t see the two being related and more of a shift left culture move.

Re: A Eulogy for DevOps

#4

Am I correct in understanding that microservices and DevOps are closely related - in that microservices trade code base complexity for operations complexity?

I would say they are both the fruit of the "ownership tree".

Both are solutions to big but specific problems.

(DevOps was a push against crazy corporate IT, where developers handed over the sacred tomes of operational manual and the blessed JAR/WAR files and IT took over from there. And operations was on-call, and ... had absolutely zero fucking idea what to do, the manuals were fake, and they had no expertise, and the whole handover was just burning money, etc. So dev teams got access, and things got a bit more programmatic anyway as scale kept growing. From the early days of Capistrano and Puppet to immutable images running on EC2 and nowadays to CI/CD with containers running wherever.

Microservies was kind of an organic step from that. Both to handle resource scaling and mostly to handle product/project coordination. Extremely limited scopes helps local reasoning to make okayish decisions most of the time.

See also Rust's ergonomics principles about "reasoning footprint" and the Bounded Context concept from DDD.

Of course the trick is that, it looks easy when someone gives a talk at a conference showcasing their company's a-ma-zing whiteboard-to-yet-another-webservice tempo, but it needs well-funded, good-faith constructive/supportive security and platform teams. And in practice it's famously hard to keep these complex interconnected systems/projects/orgs on track. And even when you have that many companies then try to force things [the good old hammer-nail anti-pattern] https://www.youtube.com/watch?v=PAew2jhr2zs )

Re: A Eulogy for DevOps

#5
> Money was (effectively) free so it was better to increase speed regardless of monthly bills.

Jesus this. No one knows where the money goes. If you can't tell me cost per customer, per user then your business is missing key metrics.

> ... "discovered" that troubleshooting Kubernetes was a bit like Warhammer 40k Adeptus Mechanicus waving incense in front of machines they didn't understand in the hopes that it would make the problem go away.

Wackamole with problems...

The part where he talks about the death of QA.. yea. This is enshitifcation in action.

Re: A Eulogy for DevOps

#6
The problem is when hardened system administrators and DBAs were replaced by people who were certainly not worthy successors. As that transition took place, a lot of the added value was eliminated.

Re: A Eulogy for DevOps

#7

The problem is when hardened system administrators and DBAs were replaced by people who were certainly not worthy successors. As that transition took place, a lot of the added value was eliminated.

But who needs to know what happens behind the facade of the services? It does everything for us!

I miss the days of having an expert sys admin and DBA to help with tough issues. Now we're all on our own with no training. Most of the good people got axed or thrown into other roles. Becoming good at something only to have it thrown away and undervalued pisses me off.

Re: A Eulogy for DevOps

#8
post #4

Am I correct in understanding that microservices and DevOps are closely related - in that microservices trade code base complexity for operations complexity?

I would say they are both the fruit of the "ownership tree". Both are solutions to big but specific problems. (DevOps was a push against crazy corporate IT, where developers handed over the sacred tomes of operational manual and the blessed JAR/WAR files and IT took over from there. And operations was on-call, and ... had absolutely zero fucking idea what to do, the manuals were fake, and they had no expertise, and t…

"And operations was on-call, and ... had absolutely zero fucking idea what to do, the manuals were fake, and they had no expertise, and the whole handover was just burning money, etc."

This is what is we with DevOps now. The short lived dev teams had it over to the next dev team with basically no documentation. DevOps was just another stop on the shitty process parade that Agile contributed to - all about speed, forget docs, who has time for real tests, and for requirements we'll just use JIRA tickets the devs work on.

Surprise, surprise... Our bug and rework stories take about 25% of our capacity now.

Re: A Eulogy for DevOps

#9

Am I correct in understanding that microservices and DevOps are closely related - in that microservices trade code base complexity for operations complexity?

Yes, in that they're complimentary methodologies. But the second you have a DevOps team (or, shutter, a "microservice team"), you've gone sideways.

Re: A Eulogy for DevOps

#10
post #4

Am I correct in understanding that microservices and DevOps are closely related - in that microservices trade code base complexity for operations complexity?

I would say they are both the fruit of the "ownership tree". Both are solutions to big but specific problems. (DevOps was a push against crazy corporate IT, where developers handed over the sacred tomes of operational manual and the blessed JAR/WAR files and IT took over from there. And operations was on-call, and ... had absolutely zero fucking idea what to do, the manuals were fake, and they had no expertise, and t…

This is such a good description. Very much appreciated.
Post reply on HN