Survival Guide for Java Architect in the Cloud Era
summary
Claims that adopting a DevSecOps culture reduces risk of fines and data breaches and treats security as prevention rather than an afterthought. Advises a cloud “flight plan” with maturity stages from none to self‑sustain, favoring pragmatic automation: use infrastructure as code plus CI/CD and Git as single source of truth so PRs run tests, deploy Java 11→17 safely and enable rollbacks. Warns against reflexive microservices adoption, recommends PaaS or hybrid clouds when teams or budget limit deep infra ownership.
AI-written summary · about
chapters (11)
- 0:00Cloud survival guide intro
- 1:28Why move to cloud
- 4:34Cloud computing models
- 8:45Cloud native definition
- 13:41Java cloud challenges
- 15:27Cloud migration flight plan
- 18:58Cloud maturity levels
- 21:02Automation and observability
- 23:54Hybrid cloud strategies
- 26:20Microservices myths vs monolith
- 28:45Q&A
related talks
10mKeynote: CloudNativeDevSecOps
50mProtecting the Cloud with the Power of Cloud
40mDevSecOps Guide to Bulletproof Your Development Workflow
45mExploring and managing risks in cloud: a practical journey to cloud security
28mWe Adopted DevOps and Are Cloud Native, Now What?
38mSecuring the Cloud
46mStrengthening Java Apps: Best Practices in Secure Coding for Java Developers
45mDon't Panic! A Developer's Guide To Security