Definition of composable architecture
“Composable”: the word says that a system is composed, piece by piece. In common usage, composable architecture refers to an information system, or a digital platform, assembled from independent components. Each component covers one function (managing content, calculating a price, collecting a payment), is exposed through APIs and can be replaced without rebuilding the whole.
The expression belongs to the vocabulary of software vendors and their professional associations. It is a matter of commercial usage, and its outlines vary from one text to another, for example on the size of a component, on how it is hosted or on the share of in-house development. It is used in contrast to the software suite of a single vendor, adopted as a block.
The MACH acronym, as read on the MACH Alliance website
The expression sits alongside an acronym, MACH. A press release published on the machalliance.org website (read on 12 November 2026) spells it out as follows: “Microservices-based, API-first, Cloud-native and Headless”, that is, based on microservices, designed first through its APIs, native to the cloud and with no imposed interface.
The MACH Alliance presents itself on this website as a not-for-profit professional association, established in 2020, which sets out principles and certifies its members, among them software vendors and integrators. The source therefore has a stake: it promotes a category of products. A page on the website reports a rebranding launched in October 2024: the future of MACH, it says, goes beyond the acronym. The website sets out three principles: open, composable, connected. It describes the second in terms of capabilities that can be assembled, replaced and evolved independently.
Composable architecture, microservices, headless, integrated software package: not to be confused
| Term | Meaning in common usage | Link with composable architecture |
|---|---|---|
| Microservices architecture | A style for building an application, as separately deployable services | It describes the inside of an application; composable assembly concerns entire products, bought or developed |
| “Headless” approach | Software that exposes content and functions through APIs and leaves the interface to other programs | One separation among others: a monolithic headless product does not make the whole composable |
| Enterprise resource planning (ERP) package | A product from a single vendor, covering several functions around shared data | The opposite term: there the vendor provides the integration, which here falls to the organisation |
On the interface side, splitting into separately released parts goes by another name: the micro frontend.
Illustration: a press group’s website and the price of assembly
Take a regional press group that is overhauling its news website. It selects four products from four software vendors: headless content management, search engine, subscription management, newsletter delivery. Its team develops the website and the mobile application, which call these products through their APIs. Later, the search engine no longer fits: it is replaced without the other three products being modified, only the website’s calls change.
Assembly leaves this press group with what a suite would have taken care of. A subscriber exists both in subscription management and in the newsletter tool: the product that acts as the source of truth must be designated. A slow page means finding out which of the four is responding poorly. Four contracts and four release schedules have to be followed. APIs become an asset to be governed, which API management provides tooling for. A change in one product reaches the others by call or by event, a mode of exchange described in the event-driven architecture entry.
The choice, function by function, between a market product and development is a matter of the “make or buy” trade-off detailed on our page custom software development. The rules that hold such an assembly together, one contract and one owner per interface, one master application per item of reference data, are those set out on our page IT architecture.