Hi @Mahesh_Gunaje ,You can use in-memory caching to optimize repeated data access. Another approach would be to store the response in a service variable.Create a Common Service with a Service Variable:Implement a service class with a Map variable to act as a cache. Store the API response in this map...

@Vishnu9 ,Glad to hear it’s working in your SPA project with the modifications you made! In our project, we dynamically load the chunk files and handle the generation of these chunk files through our Webpack configuration.output: { filename: 'theme/js/[name].js', chunkFilename: 'theme/resources/[n...

 In AEM as a Cloud Service (AEMaaCS), reverse replication is not supported. You can refer to the official documentation for more details: AEM Cloud Changes - Replication Agents.Not sure how the content gets synched between different publish pods.Third-Party Solutions: If you need to implement featur...

Hi @NageshRaja ,Yes, managing numerous environment variables can be challenging. I recommend:Create a JSON file in your code repository for each environment to store these variables.Use the Cloud Manager API to add or update environment variables programmatically.Refer to the Cloud Manager API docum...

Hi @NageshRaja , In AEM as a Cloud Service (AEMaaCS), we have only the dev, stage, prod, and rde runmodes are available - https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/deploying/overview#runmodes . Configuration can be set under the dev runmode, wit...

Follow the approaches below:Update Environment Variables in Cloud Manager:To override publish and preview domains, adjust the AEM_CDN_DOMAIN_PUBLISH and AEM_CDN_DOMAIN_PREVIEW environment variables directly in Cloud Manager.Use Custom Environment Variables:Define custom variables (e.g., CUSTOM_EXTER...

Creating a separate repository to convert the existing full-stack project to be compatible with the front-end pipeline is unnecessary. Instead, some modifications are needed in the existing project:Parent pom.xml: Update the parent POM file to remove ui.frontend from the buildContext-Aware Configura...

Did you check this documentation - https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/administering/operations/curl#replication-agent 

You can achieve this using Sling Dynamic Include. Refer to this link for more details. Write the logic on the server side to validate if the user has the correct subscription.

You don't need to run the full stack pipeline. You can use the config pipeline instead. For more details, refer to the official documentation: Config Pipeline in AEM as a Cloud Service.