What Cloud Native Java Really Means for Developers
summary
A panel discusses what “Cloud-Native Java” concretely means for Java developers, contrasting views like running existing architectures on cloud platforms, using Spring Boot/Cloud, or packaging apps in Docker and orchestrating with Kubernetes. Panelists explore which skills Java developers need to adopt (and possibly unlearn) and the concrete implications of cloud-native development practices.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:07What is cloud native?
- 6:38Cloud native vs traditional
- 9:24Managed vs microservices
- 11:33Developer experience
- 13:22Microservices and modularization
- 16:10Ops-aware development
- 18:57Java in cloud native
- 21:45Developer roles and tech explosion
- 25:36Future outlook
related talks
04mCloud-Native Java Track Introduction
51mWhat Is This Cloud Native Thing Anyway?
55mWhat Does Cloud-native Mean Anyway?
51mYour Cloud-Native Toolbox for Java
34mGoing cloud-native: Why? How? & What?
34mPanel Discussion: Cloud Native
50mCloud-Native Dev Tools: Bringing the cloud back to earth
47mLife of Java Applications in Cloud Containers