Strategy
March 9, 2026
7 min read
MACH architecture for stakeholders: a short jargon-light guide
Mikołaj Lehman
CEO & Founder
MACH is a set of principles for commerce systems: small swappable services, APIs as contracts, cloud infrastructure and headless separation of front from selling logic.
Why this is not “another shop”
Every channel (web, app, B2B partner) consumes the same domain services, we do not triple pricing logic.
Investment shifts from “theme rollout” to “API and data design”.
Costs and team
More services mean more observability and security. We budget monitoring, alerting and secret rotation.
Product owners must understand dependencies between front and back backlogs.
Migration path
We rarely big-bang, we carve the first bounded context (e.g. catalogue) and wire the existing front.
Each step has a measurable KPI (price publish time, integration error rate).
Frequently asked questions
- Is MACH only public cloud?
- No. it is about elasticity and automation; hybrid works if CI/CD stays coherent.
- How many microservices is too many?
- When coordination cost beats scaling benefits, then we consolidate domains.
- Does this fit a small company?
- Yes as “lite” headless plus one strong order service instead of a full mesh on day one.
Content updated: March 9, 2026
Share article: