Extensibility Framework for App Builder
This functional demonstration describes App Builder and its potential use cases for Adobe Commerce. This video provides an introduction to the extensibility framework, key customer benefits, and capabilities.
App Builder for Adobe Commerce app-builder-extensibility
Hi, this is Russell with Adobe. In this session, I’ll be talking about the Extensibility Framework and Commerce Eventing.
Adobe’s Commerce solutions provide the most flexibility and extensibility in eCommerce today. For Adobe Commerce On-Premises and Adobe Commerce Cloud, developers have direct access to the core code, and traditionally, this was the only method available to make changes required to meet their unique use cases. Yet that in-process extensibility comes at a cost. The more you change the Commerce application, the more difficult upgrades become.
Rising total cost of ownership and complex in-process customizations often keep customers from deploying the latest security, quality, and performance fixes that come from regular Adobe Commerce releases.
With this new method of out-of-process extensibility, we’re introducing the recommended method for custom development. This is Adobe’s Extensibility Framework called AppBuilder.
If you have Adobe Commerce On-Premises or Adobe Commerce Cloud, Adobe AppBuilder allows similar flexibility without customizing the core Commerce application. And if you’re using Adobe Commerce as a cloud solution, this is your only way to extend capabilities.
AppBuilder leverages Adobe IO Serverless Runtime to host custom services. Developers will use this framework to extend the Commerce code in an API-first cloud-native architecture. And this is Adobe’s recommended method for all development efforts.
As part of the Extensibility Framework, we provide the following capabilities.
Eventing middleware will enable developers to synchronize data between Commerce and other applications.
UI extensibility, developers will be able to build custom micro front-ends that can seamlessly be integrated into the core storefront or the back-office experience.
API extensibility will allow developers to customize out-of-the-box APIs and integrate other Adobe and third-party APIs.
The developer experience is a centralized place for the Commerce and other Adobe applications via Adobe’s Developer Console.
Mid-market and enterprise customers often use other applications in addition to Commerce to manage and run their businesses. Items such as synchronizing custom data or orders between Commerce and other applications, such as an ERP, a PIM, or a CRM.
Commerce eventing allows developers to effectively customize processes and integrate systems while maintaining SaaS-like upgradability.
This out-of-process extensibility allows for the customization and flexibility that Adobe developers demand. We provide developers mechanisms to subscribe to business events in near real-time and build integrations with third-party and other Adobe systems. This helps any project using the on-premise Adobe Commerce or Adobe Commerce Cloud without making any in-process PHP changes to the code. And once again, if you’re using Adobe Commerce as a cloud service, this is your only option to extend the functionality.
When an important change happens in Commerce, the transactional events are published as an Adobe I.O. event and they’re made available to App Builder, where the developers can build and run custom integrations with third-party applications.
Well, that’s it on this topic. Please continue to come back to Experience League to learn more about Adobe Commerce as well as all of the other Adobe products.