Share your experience using Acquia Cloud

Adobe Experience Manager is being used for website development and app PWA developments. It is also used in multiple other use cases related to creating internal web solutions and SaaS-based platforms.

DAM, Digital Asset Management, is used in hosting the entire asset collection including images, videos, and everything else. We also have a customized DAM where we upload all internal DBs related to inventories and other items. A few catalog systems are integrated, and the SKUs are typically dumped through the DAM.

Adobe Experience Manager itself is a content management system. Once you develop components, it becomes easy to change any content-related items frequently. It's very efficient in terms of getting changes done. You don't need deployment, and code changes are not required all the time.

The best feature is the experience fragment. If you want to replicate content across multiple websites with 1,000 or 20,000 pages, this feature helps accomplish it in a fraction of seconds. Additionally, there are schedulers and custom-made publishers which are handled through the system, and it's easy to integrate with multiple cloud-based platforms such as Akamai.

Regarding the component-based framework and content delivery across different platforms, we make a standard framework. Our design team members create a component library. We maintain the library as a storybook and keep it accessible to prevent creating multiple versions of the same component. We focus on reusability to save costs. If a component costs around 6 to 8 lakhs, we reduce it to approximately five, which can be replicated across multiple pages for cost savings.

Akamai has been implemented so we cannot hit the server directly. The website and pages are cached through Akamai. It hits the cache server first and serves through the cache server. When changes occur, the cache gets flushed, then replicates, and the customer receives the final copy of the page.

Adobe Experience Manager needs more optimization. The frequency of components where we have vitals of a page or an app needs to be optimized because these are heavy Java codes along with some AEM developments. The code language should be optimized or they should have some string functions or web plugins to create a lighter version rather than implementing large amounts of code lines. They should start implementing industry best practices which are not currently offered.

We perform our internal development for customization at our own pace. We have multiple frameworks that help us in various ways. We are advancing in terms of AI integration. We have already started our own POCs before Adobe implements these features.

I have been working in my current field for 12 years.

The response has been very quick. The resolution time depends on the type of ticket raised. For P1 tickets, the resolution time is approximately four hours. For P2 or P3 tickets, it takes around 8 to 10 hours TAT. The response time is quick, and they provide resolutions. If they don't have an immediate solution, they coordinate with other team members.

Positive

I have experience with Drupal and Magento, where the catalog system was used by Amazon, though they don't use it anymore. Magento is used by Flipkart and eBay. I also have experience with other custom-based solutions.

Drupal is a completely different company. While they also provide a content management system, Adobe Experience Manager is more premium, flexible, feature-oriented, and offers different templatization options where custom solutions can be built easily. Drupal has restrictions and requires a longer development process. Drupal developers are not easily available in the market. With Adobe Experience Manager, you can transition from a Java developer to an AEM developer, making resource allocation easier.

The setup process is quite flexible, with complete support from Adobe. Setting up is straightforward, and while cost effectiveness might be lacking, finding developers and implementing custom solutions is easy. You can build whatever you want across Adobe Experience Manager due to its flexibility.

The price is significantly high. It's a solution for enterprise organizations, not for small-medium organizations. Companies that are scalable and can maintain it for a longer period should consider it. These technology decisions require careful consideration because the cost can be significant. The enterprise solution is the best practice for an integrated market for Adobe Experience Manager to integrate and penetrate.

It is not cost-effective and can be expensive to implement.

I have been working with Adobe Experience Manager and other technologies including SaaS-based developments, apps, and web within the last 12 months.

Adobe Experience Manager is primarily customized development, which we handle internally, occasionally seeking Adobe's assistance for specific products or solutions used for IAM development purposes.

We run sanity suits daily across multiple platforms seeking segmentation, using custom tools and harvesting for testing purposes.

We implement content strategy through our internal portal. We have a matrix portal providing complete updates and a dashboard for tracking. We monitor the number of URLs being published, workflow progress, dispatcher status, and issue resolution frameworks. A monitoring framework has been implemented to oversee these aspects.

I rate Adobe Experience Manager a nine out of ten.

We use Liferay Digital Experience Platform for a lot of use cases. We have implemented it in oil and gas, manufacturing, petroleum, oil and gas manufacturing, heavy industries, governance, and e-governance.

The most valuable features in Liferay Digital Experience Platform are out-of-box features such as document management, low-code no-code capability, and client extensions. These are very good features of Liferay Digital Experience Platform.

I have utilized the content management feature in Liferay Digital Experience Platform, which is very good and user-friendly. Any layman can use the content management feature.

Liferay Digital Experience Platform has helped us optimize our digital presence and deliver rapid application development. Every customer is happy, and they are giving us repeat orders for whatever we have delivered on Liferay Digital Experience Platform.

I would like to see improvements in Liferay Digital Experience Platform where each feature can be loosely coupled, so I can drag and see what can be used instead of bundling the entire application. If this is possible, that would be great.

There are specific features missing at the moment regarding more integrator and LLMs, and BPM is also present. If one or two LLMs could be integrated, it would be beneficial.

I have been working with Liferay Digital Experience Platform for almost 10 to 12 years.

Regarding stability and performance, Liferay Digital Experience Platform is stable. The current version is good, but one problem is with objects where the load takes much time if the records are increasing. If there are 10 million records, then there is an issue.

With the PaaS, scalability is self-explanatory, and with the on-premises deployment, it is scalable.

My knowledge about Liferay Digital Experience Platform technical support is that there is L1, L2, and L3 support. The mail and voice support is good. The people are knowledgeable and can help with certain issues.

Positive

Before Liferay Digital Experience Platform, I used other solutions such as Drupal, PHP, and Aqua. I have experience with other platforms.

My experience with the setup process was very straightforward.

I have seen a good return on investment with Liferay Digital Experience Platform. We have reused the same kind of model in many places and have reaped the return on investment.

Regarding cost associated with Liferay Digital Experience Platform, it is a core-based application; servers are core-based systems. In India, it is a very competitive pricing market as other platforms are competing with Liferay Digital Experience Platform. AEM and other platforms are also in the market, so the pricing should be factored according to the Indian market.

The key differences that prompted me to switch to Liferay Digital Experience Platform are many. A lot of features such as workflow management and document management are absent in other platforms. The frameworks on PHP and Java are more reliable and open-source where the Liferay Digital Experience Platform application is built on.

I decided to go with Liferay Digital Experience Platform after evaluating many other options and solutions in the market. We found Liferay Digital Experience Platform more comfortable according to our customer requirements and as a digital experience platform.

The main benefits that Liferay Digital Experience Platform brings to the table are numerous. First is rapid application development and many features. Features such as content management and document management make your life easy; workflow management is also present. Workflow can be designed and derived. Form development and everything is very smooth and easy to deliver to the end customer, and you can find many features in one box. You have blogs, wikis, and everything with out-of-box functionality.

My experience with actionable insights is positive; they help in refining content strategies. The content creation is helpful. For external content creation, I use headless CMS APIs for Liferay Digital Experience Platform, and headless APIs for content creation are also available.

My thoughts on the integration capabilities are that integration is seamless. You have headless APIs where you can integrate seamlessly with any other application such as LDAP or SSO, or you can also integrate with different external systems. You have an SAP connector; everything is available.

Liferay Digital Experience Platform's open source flexibility has helped in customizing functionalities for the specific needs of my customers as it is a highly flexible application that can be optimized.

My advice for other organizations considering Liferay Digital Experience Platform is that if it's available, we need to improve on the performance, which is currently what we are seeing. Otherwise, earlier Service Builder was acceptable.

On a scale of 1-10, I rate Liferay Digital Experience Platform a 9.