MACH Architecture
Microservices, API-first, Cloud-based and Headless.
- Instead of choosing one solution, where there is a high risk of choosing the wrong one, the alliance supports decoupling the systems and Instead putting together your solution from the best, specialised solutions from around the world based on the business needs you have. As an advisor, you will only be accepted into the MACH Alliance if you have shown that you know how to work in this way.
What is behind the MACH principles?

M: Microservices
Microservices are self-contained applications that can be built, deployed and maintained as independent modular components. If there is a failure in one microservice, it does not affect your entire solution, making it more robust. Scaling and updating each component can be done independently instead of having to upgrade the entire system.

A: API-first
APIs enable integration between different solutions such as ERP and CRM in your technology suite. API-first is designed and built for interoperation, reducing the chance of silos.

C: Cloud-based
Using the cloud as a hosting infrastructure means that solutions can be easily accessed from anywhere and on-demand. Eliminates the need to operate and maintain your own data centre. Provides extra flexibility - when it's time to scale up or update.

H: Headless
Here the front end is separated from the back end. By separating the front end from the back end, you get maximum design freedom and faster prototyping.
Read more about related topics
Turn architecture into a competitive advantage with Composable Commerce
Choose the commerce solution that best suits you and your company
Digitalise your business with common sense
E-commerce, Digital Commerce or webshops? Read more here