MACH and composable architectures are quickly becoming the technical approach of choice for enterprise organisations. In this post, I'll briefly define MACH and explain how it can help you to rapidly bring new features and capabilities to market.
Why a MACH architecture is boosting enterprise agility and speed to market.
What is a MACH technology architecture?
MACH stands for Microservices, API-First, Cloud-Native, and Headless. They aren’t new terms for technology, and individually they have been an option for tech for a long time. What is new, is uniting them as a strategy for your technology architecture.
This is a strategy to create a decoupled system, as you separate your platform logic into discrete services, you remove critical dependencies and make release and updates easier, as you can change and update in isolation without redeploying the entire system.
This is a concept for the creation and management of data within the platform. As this MACH approach is focussed on Software as a Service providers, it means that although they often provide an easy to use web interface, the interface itself is built as a layer over the top utilising the same APIs you can use to integrate. Most of these APIs are becoming very familiar working with JSON data and common protocols across vendors.
In a recent discussion with a colleague we agreed that the promise of Cloud computing is starting to come to fruition, Google, Microsoft and AWS have matured their platforms to provide inherent security, scalability and performance. This means you focus on how to use the resources rather than managing them yourself.
Often used in the context of a CMS, but this means to decouple the front end technology (the viewing of the data in the marketing experience) from the management and authoring environment technology (the creation and management of the data). This separation also reiterates the microservice architecture. By creating this separation you can consume your content or data, or change the entire experience without replacing the whole backend or doing a “lift and shift”
Why is MACH becoming so popular?
MACH as a martech strategy, is helping organisations to connect the best-of-breed vendors together. Rather than looking for a single vendor to deliver the entire business requirements in a single platform, the organisation can look for SaaS vendors for specific capabilities and then connect them as a group of micro-services using the APIs to talk to each other.
This API-first approach is seen as a ‘lean’ way of working, as you are only using the platforms that deliver your specific needs. There are a growing number of Martech providers entering the market providing out of the box integrations and ‘connectors’ to help increase the speed to market and avoid developers having to recreate the wheel each time integrating systems with custom code.
Benefits of using a MACH approach to martech
One of the key benefits of using a MACH architecture is flexibility, and the flexibility spans a number of areas of the overall solution:
Rapid prototyping and feature releases
A martech MACH architecture creates the opportunity to be very agile. Should a new requirement or opportunity arise, you can rapidly prototype or develop the capability without compromising your existing systems, you can either develop the capability internally and choose your preferred technology connect the APIs how you need to and off you go, if it doesn’t work or you want to buy in, then you can bolt on a new vendor without needing to rip and replace your entire platform.
Focus and separation of concerns
With the separation of concerns that a microservices architecture and MACH approach delivers, it also gives focus to the teams who develop and use the platforms. Instead of the content authors needing to learn a bit of HTML or knowledge about testing, they can focus on writing the content that will be channel agnostic. Your developers can focus on building the experience in their preferred technology and display the content as the designers designed without having to fight against the way a certain platform works.
Stacks not suites
This is a somewhat annoying term currently used by headless vendors to push their proposition, but it applies to the MACH ecosystem. Typically when you buy digital marketing software from a vendor, you are buying a “suite” of tools and features that are great to get you started but they probably don’t deliver the breadth and depth as a vendor that works specifically to provide a certain requirement. For example, A/B testing features in a suite are rarely as comprehensive as those features from a vendor that builds specific A/B testing software.
It’s often a case that when people buy into suites, they buy into a grand vision of the future but then this vision rarely delivers to its full potential, in fairness this can often be a combination of skills, experience as well as the software itself, but the situation becomes a self-fulfilling prophecy, because the business invested in the big toolset, they are reluctant (or cant change for 3-5 years due to agreements) this causes delays and frustration.
In a MACH system, the agreements are often flexible and on a more of a “pay as you go” type model, if you need more resources as you grow, you change your agreement, if something doesn't work, change it.
I've worked with traditional Digital Experience Platforms (DXPs) for several years but the more I get into Headless and the world of MACH the more I see the opportunity to create something truly unique and focused on what our clients are looking to deliver.Steve Shaw Technical director
Software as a Service
Software as a Service (Saas) is the direction of travel that most software vendors are heading. It gives customers the freedom to use the software without needing to worry about the underlying infrastructure or those notorious upgrade projects that have haunted traditional on-premise solutions.
SaaS platforms typically have different pricing tiers, with some even offering a ‘free’ tier to try the platform with a few limitations. This makes them the perfect choice for rapid application development or proof-of-concepts projects and even those on a tight timeline where you don't want to go through a large vendor analysis and cost negotiation. Pay for what you need and scale only when you need to.
The MACH Alliance
In 2020, a number of the top SaaS martech vendors got together and formed the MACH Alliance. Their aim is to support companies in adopting the M.A.C.H. approach for their martech requirements through best practises, ideas and guiding principles.
If what you’ve read so far has piqued your interest, then I would highly recommend heading over to the MACH Alliance website (https://machalliance.org/about) and take a look at their articles and information.
A typical MACH architecture requires some core components, these include a CMS, possibly a Commerce provider and Search capabilities (for both your content and products). These 3 main elements provide the solid foundations for a digital marketing experience.
With the foundations in place you can start to connect other digital marketing capabilities which can include digital asset management (DAM), Customer Relationship Management (CRM)/customer Data Platform (CDP), marketing automation, personalisation and testing.
The beauty of the MACH approach is that you don't have to invest all at once in all the capabilities, you can connect each one as your requirements change or as your organisation evolves. This is true agile.
MACH isn't just another technology its a series of principles that organisations can use to keep them focused on delivering the best experiences they can whilst also benefiting from reduced TCO and faster speeds to market.Martin Paton Chief Technology Officer
Looking to the future
Last year Gartner produced a great piece of research content describing the "Composable Enterprise" and this is exactly what the MACH approach aims to serve. It’s a change in mindset that works alongside the digital transformation processes that many organisations are going through. From the IT foundations, through the marketing team and to management, everyone needs to be on board with an agile approach and a MACH architecture.
Developers are falling in love with the Headless CMS approach because it gives them more freedom on a project. They can build something that fits their needs exactly rather than trying to bend an existing platform into doing something it wasn't meant to.
When I’ve spoken to other developers recently I get a feeling of enthusiasm that harks back to 10 years ago when CMS platforms were a big thing. It feels like a new era of ideas and opportunity for developers and businesses alike who want to embrace a new way of working by focussing on the best experience and not worrying about being stuck on a single platform that doesn't quite fit.
Kin + Carta is a global partner of Contentful and Contentstack, two providers who we believe are leading the way in the Headless CMS space. We are also partners of commercetools who are pushing the boundaries of connected commerce solutions. All these vendors have already gained a large following and an impressive list of enterprise brands using their platforms to deliver engaging customer experiences.