Lessons Learned Migrating an Existing Product to a Multi Tenant Cloud Native Environment
summary
Adobe Experience Manager moves from JVM monoliths into Kubernetes with 37+ clusters and 177,000+ environments carved by namespaces; sidecars and init containers handle warm‑up, logging and live Log4j patching, Envoy provides per‑tenant IP/VPN, and a custom operator plus Helm and Argo Rollouts manage lifecycle and deploys. Autoscaling yields large gains: cluster autoscaler saves ~30–50%, HPA plus request‑based metrics saves ~50–75%, ARM images save 15–25%, and JVM tuning (set requests=limits, tune heap) prevents CPU throttling.
AI-written summary · about
chapters (8)
- 0:00Cloud-native migration challenges
- 3:14Multi-tenant Kubernetes namespaces
- 7:15Sidecar patterns for monolith
- 10:04Operators and Helm for environments
- 15:01Resource optimization for Java apps
- 17:09Kubernetes autoscaling strategies
- 20:42Key lessons and cost savings
- 21:47Q&A on autoscaling and JVM
related talks
39mOptimizing Resource Usage in Kubernetes
30mMigrating a monolith to Cloud-Native and the stumbling blocks
33mNavigating the Seas of Transformation: Migrating from EC2 to Kubernetes
33mSpace Invaders for Kubernetes: Consolidating 50 Clusters at Scale
39mExperiences and Lessons Learned Building a Multi-Cloud Spring Boot Backend
13mSponsored Keynote: Multi What???? Multi-cloud, Multi-cluster, Multi-tenanted K8s
42m18 Months Before the Mast
54mMigrating to Cloud Native with Microservices