Evolve18 | Abhishek Dwevidi & Varun Mitra | Introduction to the Adobe Experience Cloud and Ecommerce
•Download as PPTX, PDF•
0 likes•127 views
The document introduces Adobe Experience Cloud and ecommerce capabilities. It discusses Adobe I/O Runtime as a serverless computing platform, the Commerce Integration Framework (CIF) for integrating Adobe Experience Manager (AEM) with backend commerce solutions like Magento, and how AEM can act as a consumer of CIF services to deliver a server-side storefront and access product data from a backend system.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Evolve18 | Abhishek Dwevidi & Varun Mitra | Introduction to the Adobe Experience Cloud and Ecommerce
Similar to Evolve18 | Abhishek Dwevidi & Varun Mitra | Introduction to the Adobe Experience Cloud and Ecommerce (20)
More from Evolve The Adobe Digital Marketing Community
More from Evolve The Adobe Digital Marketing Community (20)
Recently uploaded
Recently uploaded (20)
Evolve18 | Abhishek Dwevidi & Varun Mitra | Introduction to the Adobe Experience Cloud and Ecommerce
- 1. #evolve18 INTRODUCTION TO THE ADOBE EXPERIENCE CLOUD AND ECOMMERCE Varun mitra 08/16/2018
- 2. #evolve18 2 Introduction to the Adobe Experience Cloud and Ecommerce 1 | Introducing Adobe I/O Runtime 2 | Introducing Commerce Integration Framework 3 | CIF Concepts with AEM 4 | Integrating AEM with Magento
- 3. #evolve18 3 ADOBE I/O RUNTIME: SERVERLESS FRAMEWORK FOR ADOBE 1. Adobe I/O Runtime is Adobe’s serverless computing platform based on Apache OpenWhisk. 2. Adobe I/O provides you with a flexible, on-demand, computing resource. 3. Adobe I/O Runtime allows you to create powerful event-driven applications. 4. Adobe I/O Runtime provides access to Adobe content, data, and services, orchestrate custom workflows for your business.
- 4. #evolve18 4 ADOBE I/O RUNTIME: THE PROGRAMMING MODEL • On Adobe I/O Runtime, code is executed on demand in response to Adobe I/O Events or HTTP requests controlled by conditional logic (rules). • The Runtime programming model makes use of the following entities: 1. Actions 2. Events 3. Triggers 4. Rules 5. Sequences 6. Packages
- 5. #evolve18 5 COMMERCE INTEGRATION FRAMEWORK 1. Consumer 2. Exposed CIF microservice s 3. Backend Solutions
- 6. #evolve18 6 TITLE ONLY #evolve18 5 TITLE ONLYCIFOn Cloud AEM + CIFConnector Adobe I/ORuntime + CIFon Cloud Services Commerce Backend
- 7. #evolve18 7 INTEGRATING AEM WITH MAGENTO 1. AEM • Acts as a consumer of CIF services • Delivers server side storefront • Single Page Application for Client Side Storefront 2. Commerce Integration Framework Microservices • Returns Product Data from Magneto • Returns Inventory service requests • Personalized inventory information 3. Magento • Acts as a Product Information Management System • Provided Order Fulfillment and stock management frameworks
Editor's Notes
- The Runtime programming model makes use of the following entities: Actions: Functions hosted on Runtime are called actions, executed in response to a trigger. Actions always present a single method signature. Events: Events are the entities that initiate Runtime processing. Runtime responds to events from Adobe I/O Events or direct HTTP requests. Triggers: Triggers can be used in conjunction with Rules to invoke one or more actions when called via an HTTP endpoint. Rules: Rules define the relationship between a trigger and an action, determining what actions are executed in response to the trigger under what conditions. Sequences: Sequences declare a series of actions so that a single trigger can execute the entire set. Packages: Packages bundle together a set of associated actions, and optionally feeds, and allow them to be shared with others.