Adobe ships App Builder, API Mesh and Adobe I/O Events

January 2023 gave Adobe Commerce merchants a third place to put custom code: App Builder, API Mesh and an expanded Adobe I/O Events catalogue.

Adobe ships App Builder, API Mesh and Adobe I/O Events

Extending Adobe Commerce (Magento) has always come with a trade-off. Build it in-module and you carry it through every upgrade. Stand up your own infrastructure and you carry that instead. In January 2023 Adobe put a third option on the table.

Adobe announced App Builder, a framework for building, deploying and managing custom extensions without managing the infrastructure underneath. Alongside it came API Mesh and an expanded Adobe I/O Events catalogue.

What App Builder is

App Builder is a serverless framework. Developers write Node.js functions, build custom UI extensions and manage state without provisioning servers or maintaining deployment pipelines. It ships with pre-built templates, one-click deployment, runtime isolation and built-in OAuth and secret management.

For a merchant, the practical effect is that a custom feature no longer needs its own production infrastructure or its own line in the ops budget.

What API Mesh is

Most stores pull data from more than one system. API Mesh is a lightweight gateway that lets you compose those APIs declaratively — you define which endpoints to expose, how to transform the data and how authentication works. The mesh then handles rate limiting, caching, schema stitching and failover. That is middleware you no longer have to write, or maintain, or explain to whoever inherits it.

Adobe I/O Events

Adobe expanded the event catalogue available through Adobe I/O. You can subscribe to granular Adobe Commerce events — order placement, inventory changes, customer updates — and trigger downstream systems in real time. This release added retry logic, dead-letter queues and schema validation.

What this means for you

App Builder and API Mesh are available to all Adobe Commerce customers at no additional cost, with CLI tooling, documentation and sample apps.

Nothing forces a migration. Start new work in App Builder and leave existing in-module extensions where they are until there is a reason to move them. If you are setting a 2023 roadmap, the question worth asking is which of your custom modules exist only because there was previously nowhere else to put them.