Hybrid AEM Architecture for Modern Web Frameworks | AEM Community Blog Seeding

[kautuk_sahni]

Hybrid AEM Architecture for Modern Web Frameworks by Prashant Onkar

Abstract

This blog highlights and addresses commonly faced issues while building scalable, dynamic enterprise applications using popular front-end frameworks with AEM (Adobe Experience Manager). Even though there are some tools available to address issues faced with Single Page Applications (SPA), when it comes to traditional (Non-SPA) applications, there is dearth of documentation on most of the issues faced while working with React and Angular.

Introduction
As front-end frameworks like React, Angular and Vue.js are gaining popularity, understanding the nuances of integration with headful AEM becomes imperative to the success of implementation of a content-centric enterprise application. Even though there are some tools and documentations around development of Single Page Applications using AEM and React or Angular, there is lack of information on implementing a traditional (Non-SPA) application using AEM and modern web frameworks. A typical end-user interfacing portal has following key characteristics:
1. Content-driven: Requires frequent content updates, hence business/ marketing team needs to have full control on the application.
2. Dynamic: Most of the pages have some sort of dynamic functionality which either takes input from user and makes API calls to fetch some data from third or first party.
3. SEO: Most of the pages have SEO value and drives traffic directly from search engines through deep linking.
4. Authentication: Some pages of the application require the user to be authenticated.

Read Full Blog

Hybrid AEM Architecture for Modern Web Frameworks

Q&A

Please use this thread to ask the related questions.

[pvo008]

Thanks for this @kautuk_sahni