Extensibility Framework for App Builder

In this video, we’ll be talking about the extensibility framework and the commerce eventing. As you all know, Adobe Commerce provides the most flexibility and extensibility in e-commerce today. It provides developers access to core platform code, which enables them to make any changes required to meet unique use cases. Yet that in-process extensibility comes at a cost. The more immersion customizes and extends the monolithic application, the more difficult upgrades become, raising TCO and often keeping customers from deploying the security, quality, and performance fixes that came from regular Adobe Commerce releases. With our new out-of-process extensibility framework, we are introducing an alternate extensibility framework, App Builder, which will allow similar flexibility without customizing the core commerce application. App Builder leverages Adobe IO serverless runtime to host custom services and developers can use the framework to extend commerce code in an API-first cloud native architecture without modifying the underlying core commerce application code. As part of the extensibility framework, we will provide the following capabilities. Eventing middleware will enable developers to synchronize data between commerce and other applications. With UI extensibility, developers will be able to build custom micro front-ends that can be seamlessly integrated into the core storefront or back-office experience. API extensibility will enable developers to customize out-of-the-box API and integrate other Adobe and third-party APIs. The developer experience, a centralized developer experience across commerce and other Adobe applications via Adobe Developer Console. Almost all of enterprise and mid-market customers are using other applications in addition to commerce to manage and run their business, to organize data like customers or orders between commerce and other applications such as ERP, PIM, or CRM. Commerce eventing helps customers efficiently customize processes and integrate systems while maintaining SaaS-like upgradability. Out-of-process extensibility allows for the customization and flexibility that Adobe differentiates with while mitigating divergence from supported or upgradable path, reducing TCO, and increasing agility. We provide developers mechanisms to subscribe to business events in near real-time and build integrations with third-party and or other Adobe systems without making any in-process PHP changes to the code. When an important change happens in commerce, transactional events are published as Adobe IO events and made available to App Builder where developers can build and run custom integration with third-party applications. We built a first extension demo that is running on the out-of-process extensibility framework. The Amazon Sales Channel extension enables merchants to seamlessly sell products in the Amazon Marketplace. The application is built using the two main components, the Adobe Commerce and the Amazon SP API third-party system, using the Adobe App Builder that performs a synchronization between those two systems. The application is based on user interface and actions that can be triggered either from the Adobe Commerce by changing a product pricing, for example, and for this we’re using the eventing framework or by changes in the Amazon API triggered using every minute mechanism as part of the OpenWISC platform.