DevOps for Java Developers (Or Maybe Against Them?!)
summary
Argues DevOps is less a conspiracy and more a reality: 15 years in, modern scale (projected ~175 zettabytes of data) kills faithful staging, forcing testing in production with canary deployments, feature flags and minimized blast radius. Developers must ship observable, stateless services with fast startup — think Spring Boot, Micronaut, Quarkus — and faster builds (Gradle namechecked) while adopting Developer Productivity Engineering: faster feedback, eliminate toil, automation, observability (84% report slow builds/feedback).
AI-written summary · about
chapters (11)
- 0:00The DevOps conspiracy theory
- 2:30Evidence in literature
- 6:11Who pushes DevOps?
- 8:52The definition of work
- 11:58Software craftsmanship
- 15:16The death of staging
- 20:01Testing in production
- 22:40Cloud-native readiness
- 25:50Bridging the gap
- 29:34Developer productivity engineering
- 34:18Moving forward
related talks
31mDevOps for Java Developers (Or Maybe Against Them?!)
46mDevOps for Java Developers (or maybe against them?!)
41mDevOps 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
01h 00mDevOps – Value at Speed
37mDevOps, 12 Factor and Platform Engineering
01h 01m"Doing Devops" as a politically powerless developer
