Store data request on live server. Need to refresh data on all pub servers | Community
Skip to main content
adobecq-venkat
adobecq-venkat
Level 2
May 4, 2021
Solved

Store data request on live server. Need to refresh data on all pub servers

  • May 4, 2021
  • 2 replies
  • 1030 views

Hi 

I wanted to store order data on live site. This data should be reflected on pub servers for adding additional orders in sequence.

 

I am not sure reverse replication is a good idea. What if multiple users submits at the same time to different pub servers.

 

Is database only solution?

any AEM related solutions available?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Vaibhavi_J

Hi @adobecq-venkat , 

You can use Sling Content Distribution to meet the above requirement . This distribute Sling resources between different Sling instances. This can be used to distribute/sync content between AEM Author and Publishers for different scenarios.

  • "pushing" from Sling instance A to Sling instance B
  • "pulling" from Sling instance B to Sling instance A
  • "synchronizing" Sling instances A and B via a (third) coordinating instance C

Also to answer user question, when multiple users submits at same time to different publisher, content will be pulled and synchronized between  all the publisher instance. 

For more details please have a check on below documents 

https://github.com/apache/sling-old-svn-mirror/blob/trunk/contrib/extensions/distribution/README.md

https://experienceleague.adobe.com/docs/experience-manager-65/administering/security/sync.html?lang=en#introduction

https://medium.com/tech-learnings/sling-content-distribution-in-aem-part-2-3a66933be45d

https://medium.com/tech-learnings/sling-content-distribution-in-aem-part-3-sync-distribution-sync-content-between-publishers-f6f67026fe83

2 replies

Vaibhavi_J
Vaibhavi_JAccepted solution
Level 7
May 4, 2021

Hi @adobecq-venkat , 

You can use Sling Content Distribution to meet the above requirement . This distribute Sling resources between different Sling instances. This can be used to distribute/sync content between AEM Author and Publishers for different scenarios.

  • "pushing" from Sling instance A to Sling instance B
  • "pulling" from Sling instance B to Sling instance A
  • "synchronizing" Sling instances A and B via a (third) coordinating instance C

Also to answer user question, when multiple users submits at same time to different publisher, content will be pulled and synchronized between  all the publisher instance. 

For more details please have a check on below documents 

https://github.com/apache/sling-old-svn-mirror/blob/trunk/contrib/extensions/distribution/README.md

https://experienceleague.adobe.com/docs/experience-manager-65/administering/security/sync.html?lang=en#introduction

https://medium.com/tech-learnings/sling-content-distribution-in-aem-part-2-3a66933be45d

https://medium.com/tech-learnings/sling-content-distribution-in-aem-part-3-sync-distribution-sync-content-between-publishers-f6f67026fe83

    MarkusBullaAdobe
    Adobe Employee
    MarkusBullaAdobeAdobe Employee
    Adobe Employee
    May 4, 2021

    Hi @adobecq-venkat!

    While there are different ways to store and synchronize user generated data on/between publish instances (@vaibhavi_j already pointed out Sling Content Distribution), I would not recommend any of them for actual order data in terms of e-commerce or similar transactional data. AEM and especially the publish tier is not the right place to manage or store transactions and orders.

     

    For online stores, AEM is usually integrated with some kind of e-commerce system (see [1]), e. g. leveraging the Commerce Integration Framework (CIF) [2]. There are integrations available e. g. for Adobe Commerce (aka Magento) [3] as well as many 3rd party e-commerce systems.

     

    I would highly recommend to re-evaluate your requirements and check if a different solution approach fits better than storing orders in AEM. As a general rule, storing personally identifiable information (PII) within AEM is recommended to be kept to the absolute minimum and avoided whenever it is possible.

     

    If you have to store order data, I would suggest to leverage an external system (e. g. e-commerce system or in simpler cases maybe a dedicated database) to store and manage this kind of data.

     

    [1] https://experienceleague.adobe.com/docs/experience-manager-65/commerce/home.html

    [2] https://github.com/adobe/aem-core-cif-components

    [3] https://experienceleague.adobe.com/docs/experience-manager-65/commerce/integrations/magento.html

      Terms & ConditionsAccessibility statement

      Loading footer...