Business Benefits of AEMaaCS

[AEM_Forum]

Hi all,

The Developer benefits and IT benefits of AEMaaCS are very clear.

What are the Business Benefits of AEMaaCS?

Is it just Faster time-to-value or anything else?

Appreciate all your responses.

Thanks,

Rama.

[Monendra_Singh · Accepted solution]

Hi Rama,

There are several business benefits to using AEMaaCS:

1. Scalability: AEMaaCS is a cloud-based platform, which means it can easily scale up or down to meet changing demand and workload. This can be especially useful for businesses that experience seasonal spikes in traffic or need to handle sudden increases in user activity.

2. Reliability: AEMaaCS is hosted in the cloud, which means it is less likely to experience downtime due to hardware or maintenance issues. This can help ensure that your digital experiences are always available to your customers and employees.

3. Security: AEMaaCS is hosted in a secure environment and offers multiple layers of security to protect your data and digital experiences. This can help reduce the risk of data breaches and other security incidents.

4. Cost-effectiveness: AEMaaCS is a subscription-based service, which means you only pay for the resources you use. This can help reduce upfront costs and make it easier to budget for your digital experience needs.

5. Integration: AEMaaCS can be easily integrated with other Adobe products and third-party systems, allowing you to create a seamless, end-to-end digital experience for your customers.

6. Flexibility: AEMaaCS offers a range of tools and features that can be customized to meet the specific needs of your business, allowing you to create digital experiences that are tailored to your brand and audience.

Hope this is helpful.

Thanks

[AEM_Forum]

Thanks Monendra.

I am trying to differentiate between IT benefits and Business benefits.

Some of your pointers look to be IT ones.

Ex: Scalability, Reliability.

IT benefits are very clear.

Thanks,

Rama.

[Monendra_Singh]

All good mate,

I believe overall, AEMaaCS can provide both IT and business benefits by helping businesses streamline their digital content management processes, improve their customer experiences, and save money by eliminating the need for on-premises hardware and software.

Cheers

[Mani_kumar_]

Hi @Monendra_Singh 

Main Business benefit I can see the upgrade of the system when compared to the standalone version

We don't have to be working on the sites to work on for upgrading AEM which is cost effective.

Getting integrations and Marketing will be made much more easy with AEM as cloud and other Adobe marketing tools via Adobe IO now.

Hope this helps

[AEM_Forum]

Hi Monendra,

If there is some code refactoring required in our AEM custom code, because of the new version of AEMaaCS, it is still our responsibility correct?

Adobe is responsible for only AEM.

Thanks,

Rama.

[aanchal-sikka]

Hello @AEM_Forum 

Yes, for any custom implementation, extension or overlay, its the development team that is responsible.

• If is an issue with an AEM release (noticed for multiple release), it would be pro-actively rolled back by Adobe (Its a rare case scenario, as all builds are well tested).
• If its an issue specific to a customer, rollback is not recommended. Dev teams would be requested to fix the code as per the latest release. This is important to assure all customers are on same release, thus easier management

Few more benefits, additional to the mentioned by others in comments:

1. You might also want to explore the Pre-release option with AaaCS for upcoming features https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/release-notes/prere...

It helps to familiarize with the upcoming features, thus planning your dev + delivery accordingly.

2. In Cloud Service, resource-intensive tasks related to Assets are provided via micro-services, which provides much better performance.

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/assets/overview.htm...

[Monendra_Singh]

Hey Rama,

I think Aanchal has given a detailed answer to the question.

In a nutshell, If we are using custom code in your AEM implementation and we upgrade to a new version of AEM, it is generally our responsibility to ensure that our custom code is compatible with the new version and functions as intended. This may involve refactoring or modifying our code to ensure that it is compatible with the new version of AEM and any changes or enhancements that have been made.

It is important to thoroughly test our custom code after upgrading to a new version of AEM to ensure that it is functioning as intended and does not cause any issues with the overall operation of our AEM instance. If we encounter any issues or problems with our custom code after upgrading, it may be necessary to refactor or modify the code to resolve the issues.

In summary, if we are using custom code in your AEM implementation and we upgrade to a new version of AEM, it is our responsibility to ensure that our custom code is compatible with the new version and functions as intended. This may involve refactoring or modifying our code as necessary.

Cheers