The Exadel Marketing Technology team has delivered a wide variety of projects using AEM. Despite the wide range of projects, we have identified some common areas of AEM on which effective project management and execution rests. These are: AEM architecture and design, AEM performance issues and scalability, AEM maintenance and support, AEM security, AEM customer experience and content strategy, and automation. Obviously, there is no easy fix for issues in any of these crucial areas, so improving the foundation of your AEM strategy may take time. AEM best practices for critical areas | AEM architecture and design Choosing the right storage architecture for your Adobe Experience Manager (AEM) deployment will help your system’s performance and reliability. The basic rule is that TarMK is designed for performance, while MongoMK is used for scalability. Develop a SOLID architecture. Compliance with SOLID principles should result in a system that has a strict separation of concerns. It is important to keep AEM platform upgrades in mind while designing solutions, especially when you plan to extend OOTB behaviors. Always apply customizations in the /apps directory and either overlay on top of the corresponding nodes in the /libs directory or use sling:resourceSuperType to extend the out of the box behavior. While some modifications may be needed to support a new AEM version, the new version should not overwrite your customizations if you’re following this practice.
Please use this thread to ask the related questions.
Topics help categorize Community content and increase your ability to discover relevant content.