The Past, Present, and Future of Adobe Experience Manager
summary
Adobe Experience Manager now emphasises cloud-native delivery: more API traffic than page renders with more JSON than HTML and first-class GraphQL for content fragments shipped to both Cloud Service and AEM 6.5 (service pack). Cloud Service auto-scales, uses a CDN (Fastly) to upload large assets at edge so a 500 MB upload becomes ~30s instead of many minutes, and adds an image-transformation service. Quickstart code is ~1/3 smaller while orchestration code grows ~2x; extensibility shifts from OSGi bundles to webhook/Adobe App Builder models and jQuery dependency is being removed.
AI-written summary · about
chapters (5)
- 0:00Welcome and introductions
- 3:56Evolution of AEM over years
- 10:17Cloud and headless innovations
- 14:27Empowering developers with AEM
- 25:45Q&A with Adobe team
related talks
52mKeynote: Headless Today & Tomorrow with Adobe Experience Manager
01h 00mBuilding next gen composable services with Experience Manager
02mAEM Shorts: Modernizing Your AEM Implementation with Cloud Service
39mAdobe Experience Manager as a Headless CMS - Where/When/Why?
54mAdobe Experience Manager Rock Star: The Headless Challenge
02mAEM Shorts: Driving Headless Experiences with AEM
38mSeamless Integration of Experience Manager Assets with Applications
54mFireside Chat with Experience Manager Product Leaders