AEM logic layer

[Harry-gee-three]

Afternoon

We have been advised by a couple of a consultancies that we should not build logic in AEM. Particularly around routing emails and copy corresponding to middleware error codes.

can I ask for some expert guidance on how others have filled this gap in logic in AEM? We have done this in AEM because the other options we were presented with in our product set was in launch or to purchase Adobe forms.

thank you

[sherinregi · Accepted solution]

Hi @Harry-gee-three 

AEM is predominantly tagged as a content management system and is setup in a way to deliver the best digital experience to the customers. The architectural setup in AEM which consist of author publish and dispatcher is also focuses more on delivering the rite content also with a better response time with all the caching in place. This is one of the reasons to limit serving dynamic logic from AEM.

One of the approaches you can look for implementing custom logic and integrating the FE in AEM would be microservices which can be light weight and deployed/hosted on cloud providers/on prem which can be scaled as per your needs and also keeps you AEM servers healthy. 

On the ever evolving AEM cloud offering also we can see many of the costly operations have been decoupled from core AEM to microservices to improve the overall system.

[ManviSharma]

Hi,

AEM is primarily a content management system and should be used for managing and delivering content. Complex logic, such as routing emails and handling middleware error codes, is better suited for middleware or backend systems.

1. Use middleware for email routing and error code handling.
2. Leverage AEM for content management.
3. Consider Adobe Forms for advanced forms.
4. Custom solutions are an option.
5. Prioritize scalability and maintainability.

[HarryGeeThree]

thank you both