Adobe Experience Manager Review

Easy to use content management platform for anyone requiring a complex web portal


What is our primary use case?

In general, we work a lot with software requests by our customers, mainly enterprise companies. Typically, our clients are in supplies and they require a complex web portal. They are demanding in terms of quality and usually prefer to work with Adobe and not with Drupal or other platforms because here in Italy, Adobe has a lot of commercial support. We manage a software factory with over 150 employees. We are customers of Adobe and I'm a chief technology architect. 

What is most valuable?

I'm quite happy with the platform. It requires particular skills, so it's not so easy to prepare or find resources to specialize in it but with the right resource system and the right competencies, it's easy to work with. 

What needs improvement?

The programming model could be improved, it's a monolithic solution and that's what we don't like. Some features are badly defined in the solution. It's difficult integrating so we're forced to develop other APIs in order to simplify things. It's a weak feature of the product. 

How are customer service and technical support?

Adobe usually don't want to speak to the integrators, they want to speak with the client. That's the approach in Italy. I don't know if the commercial strategy is different in other countries, but in Italy we had lots of issues when we tried to talk directly with Adobe. It's not so easy. Typically, any issues are inherent to knowledge about the platform. If the issue is that something is not working as expected, we usually discover the problem is linked to the fact that we don't know the platform well. That's when we ask for support and usually with some configuration, or by using the platform in a different way, we are able to fix or bypass the issue.

How was the initial setup?

The initial setup usually takes somewhere between five and nine months. Typically these portals require a lot of time and in my opinion, implementation depends more on the type of projects, rather than the type of web content management system. We prefer to manage directly on the AWS environment, which our clients typically already have. 

What other advice do I have?

Adobe is a more expensive solution than, say, Liferay. But we don't like the portal approach in Liferay, it's quite old. We've worked on our portal CMS since 2010, so it's been over 10 years. In Liferay, the core is still based on portal frameworks which is a disadvantage because we know that to develop something with that model is quite expensive. In general, our employees are more familiar with Adobe and have more confidence using that solution. 

I would rate this solution an eight out of 10. 

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
**Disclosure: My company has a business relationship with this vendor other than being a customer: Integrator
More Adobe Experience Manager reviews from users
...who compared it with Drupal
Add a Comment
Guest