Characteristic of a MACH architecture
A MACH architecture almost always consists of manageable components. This makes the architecture open and accessible to all kinds of applications and extensions. MACH stands for Microservices, API-first, Cloud-native SaaS and Headless. Hence, we love it at BTTR; it contains almost all the elements that we currently believe accelerate innovation.
Need help setting up your MACH architecture?
-
01 Microservices
Microservices or Microservice architecture is a way of software development in which the architecture is built from all kinds of small applications that work together in a smart way. These small partial applications form one whole for the user because they are addressed from one front-end application. Read more about Microservices here.
-
02 API-first
All sub-applications used in the microservice architecture are accessed through structured APIs. The quality of APIs is therefore becoming increasingly important. API-first thinking when building an application is therefore essential to making a MACH architecture approach successful.
-
03 Cloud-native SaaS
To get started with a MACH architecture, it is important that all applications that are part of the IT landscape are Cloud-native. We call these applications Cloud-native SaaS applications. This way, your architecture allows you to access and address the APIs needed within your landscape anytime, anywhere.
-
04 Headless
To make your MACH architecture one logical entity, it is important to work headless. That means the front-end should be separate from the back-end. The function is separate from the visible front-end. Each application within your landscape has its own separate function but this function is unlocked in the front-end; the environment where your IT landscape comes together.
