Service and Support
Adobe Experience Manager customer support is generally quick, with resolution times varying by ticket priority. P1 tickets see a resolution in about four hours, while P2 and P3 take 8-10 hours. Customers rate support highly, praising responsive, knowledgeable teams. There are experiences of delays and challenges with custom code support. The community is valuable, and dedicated account-specific support is often beneficial. However, mid-sized companies experience less direct contact.
Deployment
Adobe Experience Manager's initial setup is generally straightforward for many users, especially with Adobe's customer support. However, it can be complex and costly for smaller organizations or when requiring custom solutions. Training and understanding of technologies like Sling and JCR are often necessary. For cloud services, Adobe handles most configurations, making it less time-consuming. While some users report challenges, others find setup manageable with the right planning and knowledge.
Scalability
Adobe Experience Manager is praised for its scalability, effectively supporting large teams and handling organizational growth. It excels in reducing infrastructure and maintenance costs, offering flexibility in design and development. Despite some difficulties in cloud migration and licensing requirements for expansion, it provides auto-scaling capabilities. Users appreciate its ability to manage content efficiently and customize templates and components, supporting numerous projects and expanding user needs.
Stability
Adobe Experience Manager is stable and reliable, especially in well-configured environments. Memory leaks and integration issues are occasionally noted, often due to custom code or architecture problems. It efficiently handles high-traffic sites and complex workflows. Its stability can be affected by storage consumption, but quick response time and robust security ensure high performance. Users appreciate the smooth upgrade experience, particularly in enterprise settings, where stability is crucial.
