The resources collected in this repository aim to enable software developers to lead their company’s transformation to a composable web architecture following MACH principles. This includes:
- Interoperability standards and reference materials which facilitate easy integration and collaboration across various platforms
- Typical platform categories and the roles of each platform in a composable digital solution landscape
- Reference architecture diagrams and entity samples to illustrate and support interoperability, which aim to ensure a smooth and cohesive digital ecosystem
Brought to you by the MACH Alliance Interoperability Task Force
- What are the MACH principles?
- Guidance for software architects and technology leaders
- Reference materials
- Contributing
- Interoperability Task Force members & contact
The MACH Alliance promotes a technology ecosystem that is based on four key principles: Microservices-based, API-first, Cloud-native SaaS, and Headless. These principles ensure maximum flexibility, scalability, and interoperability for digital commerce platforms and other business applications.
-
Microservices-based: Microservices architecture breaks down a traditional monolithic application into smaller, independent services that are easier to develop, deploy, and scale.
-
API-first: An API-first approach means that applications are designed with the intention of being accessed and interacted with primarily through APIs. This promotes ease of integration and extensibility.
-
Cloud-native SaaS: Cloud-native software is designed to take full advantage of cloud computing capabilities, such as scalability, reliability, and flexibility. SaaS (Software as a Service) refers to software that is delivered over the internet, rather than installed on-premises.
-
Headless: Headless technology decouples the front-end and back-end of an application, allowing for greater flexibility in how the user interface is built and delivered.
By adhering to these principles, the MACH Alliance aims to foster an ecosystem of interoperable, best-of-breed technology solutions that empower businesses to build flexible, scalable, and future-proof digital platforms.
Not sure where to start on your composable implementation journey? We recommend referencing these guides in the order they appear here. Dive into reference materials and diagrams for additional detail.
These guides introduce composable architectures at a high level, providing reference architectures and guidance on evaluating and integrating technologies.
| Asset | Format | Description |
|---|---|---|
| MACH interoperability hub | Hub | Central hub for resources and information related to MACH interoperability standards (on the MACH alliance website) |
| Introducing MACH interoperability standards | Blog | Intro and the big why of MACH interoperability |
| Part 1: How to evaluate and integrate composable solutions | Whitepaper | Principles for evaluating systems and approach + what to do with non-conforming legacy systems |
| Part 2: MACH Reference Architecture Introduction, | Readme | The Path to Composable Ecosystems, introduction to the MACH reference architecture, explaining its components and benefits. |
| Part 2.1: MACH Reference Architecture detailed: How to design a MACH ecosystem | Readme | Detailed guide on designing a MACH ecosystem, including architecture components and best practices. |
| Part 3: Understanding composable architecture, key concepts and patterns | Whitepaper | Technical Guide detailing component and platform integration concepts and patterns in modern digital ecosystems |
| Diagram MACH Reference Architecture for Composable Ecosystem | MACH Reference Architecture in three levels of detail: Domains, Platform categories, Platform repsponsibility | |
| Reference Architecture diagram generator | Tool | Code-first Composable Architecture Diagram Generator including code first samples for 3 detail levels of the MACH reference architecture. generator documentation |
Coming later. These guides will describe how to transition to an composable architecture as an organization.
Coming later. These guides will describe at a detailed component level how to implement a composable architecture, as well as expectations for system interoperability.
-
Platform definitions: defines three-letter-acronym platforms you’ll come across frequently in MACH materials.
-
Platform roles guidance: See High detail version of reference architecture for Platform Responsibility definitions
-
Materials we’ll add in the future:
- Entity reference
- Canonical Data Model (CDM)
- Interoperability Protocols best practice
- Interoperability Terminology
Before contributing to this repository, please read the Contribution Guide
Get in touch with the task force:
| Person | Role |
|---|---|
| Chris Bach | Co-founder/CSO, Netlify & Executive Board Member, MACH Alliance |
| Adam Peter Nielsen | CTO, Novicell & Technology Council Member, Interoperability Task Force Lead, MACH Alliance |
| Daniele Stroppa | Senior Partner Solutions Architect, AWS & Technology Council Member, MACH Alliance |
| Dom Selvon | CTO, Apply Digital & Executive Board Member, MACH Alliance |
| Filip Rakowski | Co-Founder/CTO, Alokai & Technology Council Member, MACH Alliance |
| Mark Demeny | Sr Dir, Product Management, Yext & Tech Analyst, MACH Alliance |
| Ramon Snir | Staff Product Manager, Netlify & Technology Council Member, MACH Alliance |
| Roberto Carrera | Strategy Architect, Apply Digital & Technology Council Member, MACH Alliance |
| Subhasri Vadyar | Technology Architect, Valtech & Technology Council Member, MACH Alliance |
Interoperability Task Force co-leads: Adam Peter Nielsen & Ramon Snir