Ecommerce Architecture and MACH

Composable Commerce keeps components swappable and avoids vendor lock-in

The era of rigid e-commerce monoliths is coming to an end. Modern online retailers rely on Composable Commerce: an architectural approach where the best specialised solutions (best-of-breed) for checkout, CMS, PIM, and ERP are flexibly connected via APIs. The technical foundation for this is MACH, short for Microservices, API-first, Cloud-native, and Headless.

This accelerates time-to-market and makes new channels (Social Commerce, mobile apps, IoT) easier to cover, without re-platforming the entire system. MACH is not a technology but an architectural decision: each building block can be replaced, scaled, and updated independently.

Anti-Patterns: The Limits of the Monolith

• The Upgrade Prison: Security updates or feature enhancements to the core system are so risky and expensive that they are deferred for years.
• Slow Frontend: The tight coupling between backend logic and presentation leads to bloated pages and poor performance (see Core Web Vitals).
• Feature Overkill: You pay for hundreds of features in the e-commerce suite, of which only a small share is actually used. Unused functionality drives licence and maintenance costs; whether it weighs on performance only a concrete profiling exercise will show.

The Four MACH Pillars

1. Microservices: Each function (checkout, product catalogue, search) is an independent, separately deployable service.
2. API-first: Business capabilities are exposed through APIs as a first-class contract. The frontend is decoupled from them.
3. Cloud-native: Services are built from the ground up for cloud operations, with automatic scaling and managed-service infrastructure.
4. Headless: The frontend is fully decoupled from the backend. Any frontend (web, mobile, voice, IoT) consumes the same APIs.

Composable Commerce in Practice

1. Best-of-Breed Selection: Choosing the optimal tools for each area (e.g. Algolia for search, Contentful for content, BigCommerce or Shopify for checkout).
2. API Orchestration: Building a central layer (middleware) that coordinates the data flow between the various services.
3. Omnichannel-Ready: Because the logic is centralised, new sales channels can be easily plugged in.
4. Micro-Frontends: Decomposing the user interface as well into independent components for higher development speed.

Advantages and Challenges

The advantages lie in agility:

• Vendor Independence: Best-of-breed selection per function instead of dependence on a single platform vendor.
• Faster Innovation: Individual services can be updated without affecting the overall system.
• On-demand Scaling: The checkout service can be scaled independently on Black Friday.
• Team Autonomy: Each team owns its service end to end (bounded context).

These come with real challenges:

• Orchestration Complexity: More services mean more integration and operational overhead.
• Higher Initial Investment: Composable migrations are costly and require a clear TCO analysis.
• Skill Requirements: Requires expertise in API design, cloud infrastructure, and microservices operations.

The Focus: Business Agility

Composable Commerce allows individual building blocks of the system to be replaced or improved without putting the overall system at risk. This lets MACH systems respond to market changes faster than a monolith ever could.

FAQ

Won't maintenance become much more complex if we have so many different tools?

Complexity shifts from programming to orchestration. Maintaining individual, specialised tools is, however, significantly simpler and lower-risk than caring for a giant monolith.

Can we still manage our marketing campaigns ourselves in a Headless system?

Yes, even better. Modern Headless CMS often offer more intuitive editing interfaces and a preview function for all channels simultaneously.

References

• BigCommerce Headless Commerce Guide. A technical guide for those starting with headless commerce architectures. (2021). www.bigcommerce.com/articles/headless-commerce/
• MACH Alliance MACH Architecture Principles. The organisation behind the MACH standard promotes open, cloud-native, and Headless technologies (Microservices, API-first, Cloud-native, Headless). (2020). machalliance.org
• Gartner Composable Commerce. Gartner research on Composable Commerce as an architectural approach for modern online retail. (2020). www.gartner.com/en/information-technology/glossary/composable-commerce

---

Related topics

• Technology: API-First, the interface context for a MACH architecture.
• Innovation, the innovation section that frames composable architectures.