7 Ways to Break AEM
summary
This talk examines concrete ways Adobe Experience Manager (AEM) installations can fail or degrade: component counts that make pages uneditable, large numbers of user groups versus long ACLs, maximum JCR child nodes and their performance impact, deep resource type inheritance, many workflow instances or live copies, oversized change-sets for commits, and misbehaving Health Checks. It also covers monitoring strategies and tools to observe AEM behavior as these failure modes occur.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 4:10Breaking AEM basics
- 9:38Scripting and automation risks
- 16:48Component and caching issues
- 22:19Performance and latency problems
- 27:41Tracking and monitoring pitfalls
- 30:56Security and health checks
- 35:53Usability and prototyping
related talks
28mDeep dive into AEM as a Cloud Service continuous delivery model
30mContent Upkeep
19mEfficient Sites Structure – Improved Performance
23mDelivering commerce experiences at scale
51mAnalyzing Architectural Risk
52mNot on Our Watch: an Introduction to Application Performance Monitoring
39m30 minutes of Failure
01h 00mBehind the scenes of Adobe Experience Manager with SRE guild members