Why should you learn more about App Builder

Since Adobe Commerce is not a fully SAAS product, the code you develop can add complexity and upgrade issues. By using out-of-process extensibility, such as App Builder, you can provide custom, unique functionality to your Adobe Commerce store without requiring in-process methods.

Other benefits include:

  • Decoupled features allow for faster time to launch.
  • Upgrades are now easier. The custom features are outside the Commerce codebase, which prevents compatibility issues when upgrading.
  • Moving features and logic outside of Commerce frees up resources that are normally used by in-process development methods.

Architecture

Instead of an out-of-the-box solution, Adobe Developer App Builder provides a common, consistent, and standardized development platform for extending Adobe Cloud solutions such as Adobe Commerce including:

  • Adobe Developer Console used for custom microservice and extension development. Build and manage projects while accessing all the tools and APIs needed to create plugins and integrations.
  • Open-source tools, SDKs, and libraries to build custom extensions and integrations. Use React Spectrum (Adobe’s UI toolkit) to have one common UI for all Adobe apps.
  • services such as I/O Runtime for hosting infrastructure on Adobe’s serverless platform and I/O Events for event-based integrations. Adobe also provides out-of-the-box support for storing data and files.
  • Adobe Experience Cloud where you submit extensions and integrations to publish in your Experience Cloud Org. System admins can review, manage, and approve these extensions. Once published, your custom App Builder extensions and tools are available alongside other Adobe Experience Cloud apps.

The following diagram illustrates how a standard application built on App Builder uses these functionalities:

Architecture

For more details about the App Builder architecture, see the Architecture Overview.