Upgrading an AEM cluster deployment using Docker
summary
Docker images hold libs/apps inside the container while the rest stays on a shared repository, using Oak Composite Node Store to mount a private read‑only app layer and a shared content layer. Upgrading means replacing containers rather than dropping jars, so libs/apps are immutable at runtime and upgrade tasks cannot run during rolling upgrades. Strategy requires deferred shared‑repo migration, strong backward/forward compatibility, avoidance of rollbacks, and choosing rolling/blue‑green or maintenance windows; a 6.4 SP1 Docker image and ~30 beta requests exist.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:30Current challenges
- 3:32How can Docker help
- 4:50Composite Node Store
- 6:00Challenges
- 7:15Composite Nodestore
- 8:32Upgrading
- 9:08Problems
- 11:25No explicit upgrade mode
- 12:20New content
- 13:51Rollback
- 15:24Guidelines
- 15:55Summary
- 17:24Upgrading in the cloud
- 18:40Docker Beta Program
related talks
28mDeep dive into AEM as a Cloud Service continuous delivery model
30mContent Upkeep
22mApplication Hickory Dickory Docker!
34mStaying Current A Journey in Software Maintenance
38mMigration from Old Java-EE App to Modern Cloud Native Apps
01h 20mExtreme Makeover - Application Edition
53mThe Road to Continuous Deployment: a Case Study
40mModernizing the Legacy