DevOps for Java Developers (Or Maybe Against Them?!)
summary
Argues DevOps originates in ops but becomes developers’ problem because production quality now defines “done,” adding on‑call, observability, feature flags, stateless/scalable design, and cost-conscious engineering. Cites concrete wins: 50% savings with Kafka on cross‑AZ traffic and elite teams achieving 2008x faster releases; notes hiring demand with ~40,000 U.S. DevOps openings and AWS DevOps certification. Recommends learning cloud/Kubernetes, embracing SRE practices, and building repeatable, fast builds and observable, rollbackable services so fixes actually work in production.
AI-written summary · about
chapters (9)
- 0:00Introduction to DevOps
- 3:10DevOps origins and Phoenix Project
- 8:11DevOps as ops rebranding
- 11:45Dev vs Ops work boundaries
- 16:42Quality shifts to production
- 20:40Developer responsibilities in DevOps
- 23:35DevOps benefits for business
- 26:31DevOps as collaboration
- 29:02Future of DevOps
related talks
41mDevOps for Java Developers (or maybe against them?!)
37mDevOps for Java Developers (Or Maybe Against Them?!)
46mDevOps for Java Developers (or maybe against them?!)
44mDevOps for developers (or maybe against them?!)
57mDevOps for developers or against them. Barukh Sadogursky. Java Fest 2020 Online
30mDevOps In A Cloud Native World
24mHow DevOps changed the way we operate software
45mWhat is DevOps and why should you care?
