AEM Content & Commerce using the Commerce Integration Framework (CIF) provide a flexible architecture to connect AEM with Adobe Commerce or any other commerce solution – commercial vs home-grown. Project Firefly and GraphQL play an essential role for AEM Content & Commerce and the CIF.
10/5/21 13:00 PDT 10/5/21 22:00 CEST
Mark J. Becker
Project Firefly - Adobe.io
Please use this thread to ask the question related to this Session.
Hello @Markus Haack and team,
Thank you very much for the detailed explanation of the integration reference. We are currently evaluating solution architecture of an AEM based SPA storefront which will have SFCC as it's commerce engine. We will also be leveraging content services to fuel native APPs as well.
We are evaluating this integration reference as the most prominent integration approach. As elements such as SPA and APPs are involved, just wanted to know your suggestion/recommendation on the same. Would really appreciate if you can provide any additional resources/references as well.
Happy to discuss further if needed.
@sbhazra thanks for reaching out. Our planed setup and architecture of an AEM based SPA storefront connected to SFCC totally makes sense. We have other customers using similar line-ups, only with different commerce engine.
With CIF toolbox you have to choice of picking only the parts you need. See How CIF Integrates with Adobe Commerce and Third-Party Commerce Solutions for more details on the different integration options. We also provided a small reference project to help you getting started with building an integration for SFCC.