~/talk

Lessons Learned Migrating an Existing Product to a Multi Tenant Cloud Native Environment

links:none on file
slides:none on file

Adobe Experience Manager is reworked into a multi-tenant, Kubernetes-based platform running on >37 clusters across regions and supporting ~17,000 customer environments (one environment per namespace, often a “micro‑monolith”). Builds use sidecars for caching, logging and Envoy tunneling, init containers for emergency patches (Log4j), a custom reconciler operator that orchestrates Flux + Argo Rollouts and security profiles, and optional Kata isolation. Key operational lessons: set JVM heap to ~75% of container, tune requests/limits to avoid throttling, and consider 15–25% ARM savings for images and nodes.

AI-written summary · about

  1. 0:00Multi-tenant migration challenges
  2. 3:12Adobe Experience Manager on Kubernetes
  3. 10:20Security and isolation in clusters
  4. 14:52Scaling customer environments
  5. 17:19Optimizing Java workloads on Kubernetes
  6. 28:01CPU requests and limits in Java
  7. 32:20Auto-scaling Kubernetes workloads
  8. 36:18Key takeaways
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.