Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.

SPA and Server-Side Rendering | AEM Community Discussion




SPA and Server-Side Rendering by Adobe Docs


Note: The Single-Page Application (SPA) Editor feature requires AEM 6.4 service pack 2 or newer.
The SPA Editor is the recommended solution for projects that require SPA framework based client-side rendering (e.g. React or Angular).

Note: AEM or later is required to use the SPA server side rendering features as described in this document.

Single page applications (SPAs) can offer the user a rich, dynamic experiences that react and behave in familiar ways, often just like native applications. This is achieved by relying on the client to load the content up front and then do the heavy lifting of handling user interaction and thus minimizing the amount of communication needed between the client and the server, making the app more reactive.
However this can lead to longer initial load times, especially if the SPA is large and rich in its content. In order to optimize load times, some of the content can be rendered server-side. Using server side rendering (SSR) can accelerate the initial load of the page and then pass further rendering on to the client.

When to Use SSR
SSR is not required on all projects. Althgouh AEM fully supports JS SSR for SPA, Adobe does not recommend implementing it systematically for every project.
When deciding to implement SSR you must first estimate what additional complexity, effort, and cost adding SSR realistically represents for the project, including the long term maintenance. An SSR architecture should be chosen only when the added value clearly exceeds the estimated costs.

Read Full Blog

SPA and Server-Side Rendering


Please use this thread to ask the related questions.

Kautuk Sahni

Topics help categorize Community content and increase your ability to discover relevant content.

0 Replies