Acquia Digital Experience Platform vs Adobe Experience Manager

• The Acquia Cloud Hosting (enterprise) provides a three-server solution. You have a Development, Staging (or UAT), and Production servers with a clear path of deployment straight up the chain. You may use Acquia's own Cloud Hooks, or their web admin UI interface to deploy to any or all of the servers.
• Git is one of the foundation services built-in to the management of the website codebase. Allowing a developer, or well-trained end user (university employee) to easily deploy a tag or branch to any one of the servers, makes it very easy for us to offload the server / account management to the school, while we focus on improving their site.
• Not only does Acquia Cloud provide a multi-datacenter failover disaster recovery solution, but they also maintain a multi-region failover as well, which allows for a fully redundant enviroment to be maintained in two geographic regions. No fear of losing any database changes or form submissions from students.
• Lastly, the onboarding process is constantly being improved, and as I have been a third-party vendor involved in many of our hosting negotiations, I have seen it firsthand. Each enterprise client is assigned a small team of engineers, technical leads, and a pseudo-project-manager to explain the process in layman's terms to the client (university / college for my example), but they also perform a number of code reviews and best-practice analysis of a site prior to launch.

Read full review

• Content and assets are managed effectively with AEM, which allows team members to utilize this content effectively.
• Moreover, as it is part of the Adobe suite, its integration with other Adobe products such as ACS is very easy and effective, compared with others.
• Components availability

Read full review

• Responses from tickets aren't always from the same person, and can vary in effectiveness of solving your problem
• While documentation is robust, it can be difficult to find exactly what you need
• Provided forums are not monitored frequently, and are not as useful as they could be

Read full review

• The new Touch UI interface could use a lot of improvement. Many of it is smaller detail items/features, but when using the system extensively it can become cumbersome.
• There is a bit of a learning curve because of the depth of what Adobe Experience Manager can do. Even basic editing and page creation, while relatively simple at the most basic level, is not as intuitive and easy to use as other systems like Wordpress.
• Development can be complicated. Although I've not personally done much in terms of dev work, my experience and what I've heard from my colleagues indicates that there are some complexities that make it not as easy to develop in as other systems.
• The source edit option within the rich text editor does not include syntax coloring for the code, or even a different serif/monospaced font. It is the same sans serif font as the regular rich text, which makes it hard to read.

Read full review

• Our website isn't a revenue generator, so we don't have specific ROI calculations.
• The new website is helping us move off of a legacy on-prem server environment. The reduction of cost in maintaining those will be beneficial.
• We have had to invest in some training for our developers to learn Drupal.

Read full review

• We have been able to meet our first objective of rolling out a site to replace our current Students site well within time parameters
• We were able to deploy the site to replace our County Offices within three months, and the users have been able to turn out acceptable content

Read full review