7 Ways to Break AEM

Wednesday, 12. September 2018 14:50 - 15:20 (30 min)


Most days we try to keep things running - this is sometimes challenging, especially if you don't know when things start to break. So let's break it!

How many components on a page will make a page "uneditable"? How many groups can a user have until you feel the performance impact? Or should you rather have fewer groups and longer ACLs in the content? What is the latest regarding maximum sub nodes in JCR and what is the actual impact of having many? Is there any performance impact of having many resource type inheritance levels? Can you break the system with many workflows instances or live copies? Is there a limit on how big a changeset can be for one single commit? Can a badly implemented Health Check break the system?

The talk will not only break things but also show options on how to monitor AEM while things go wrong. Expect the unexpected.


Georg Henzler Georg Henzler, Netcentric

Back to schedule