MACH Alliance March

by Jay Cuthrell
Share and discuss on LinkedIn or HN

This week we’re going to look back at the MACH Alliance and the future ahead for Enterprise software application experiences.

Getting Informed

First, MACH isn’t related to Earst Mach or feeling the need or something to shave facial hair or a microkernel…. However, MACH Alliance did recently publish MACH Global Research 2024.

Oh, wait. You might be wondering what MACH Alliance is. Well, according to the MACH Alliance LinkedIn page which has ~18k followers…

The MACH Alliance advocates for open and best-of-breed enterprise technology ecosystems.

What’s that? Ohhhhh, right.

You may be wondering what MACH itself is. MACH is a clever backronym-style acronym that conveys an association with the need for speed… of innovation.

  • Microservices (based)
  • API (first)
  • Cloud (native and most likely SaaS)
  • Headless (like the flat file CMS + 11ty + GitHub + Netlify + Cloudflare experience at fudge.org)

Clever, right? Well, let’s get back to the MACH Alliance for a moment… In the past four (4!) years, the members have grown from eighteen (18!) members with a manifesto into a growing 100+ members by 2023 and now representing a who’s who in the Enterprise software application experience zoo for the future.

Jay, get to the point…

What does this mean? Well, it might mean that Enterprise software application experiences are going to be vastly improved year over year as MACH architectural choices are made, executed upon, and iterated continuously with a feature-flag opinionated inclusion of feedback telemetry as part of an overall product-led growth mindset.

So, are Enterprise apps bad now? Well… most are not awesome but there is no need to name names — that’s truly not the point. The point is that moving from web-first to mobile-first to API-first to data-first to design-first and the interpolation thereof were all generational patterns of progression for state-of-the-art.

Does this conjure images of bone-wielding apes and the appearance of a monolith? Well… tear down that monolith.

Example: Ask yourself these questions if you are in a large Enterprise company and not on the software application team or the SRE on duty who knows the stack backward and forward.

  1. Have you ever seen a typo, quirk, error, or omission on your company website, app, landing page, etc… and felt powerless to correct it ??
  2. Have you ever tried in vain to figure out how to get something wrong in a software application fixed ??
  3. Have you ever felt like “opening a ticket” was like shouting into a trashcan or the great abyss of IT, Marketing, Communications, and Third-party agency feedback loops to nowhere?
  4. Have you ever felt like the organization around you rolls out software updates at what should be timely but instead at a glacial pace ??
  5. Have you ever felt that with Enterprise software… Things. Should. Not. Be. This. Hard. Slow. Error-prone. Underwhelming. Awful. ??

A new (~4-year-old) hope…

Notably, Gartner covered MACH last year and has once again predicted that pioneering digital leaders will deliver on initiatives by embracing composable architectures… like MACH.

Or, in a nutshell…

“You’re will you will die if you cannot get ahead of the curve and innovate at speed at which you can still surprise & delight your customers” – Jasmin Guthman of Contentstack

Source: Marketing in the Madness with Katie Street

As you might imagine, Many of these MACH Alliance member companies have written explainers on MACH and why it matters.

The future of MACH…

Of course, architectures have effective lifespans and there are inherently going to be choices within any architecture. Will adopters of MACH have regrets and reviews to share in the coming years? It is hard to say since MACH architecture is not necessarily a mandate for specific infrastructure decisions.

If you remember the first time you heard someone say phrases like front-end or back-end or full-stack, you’ll appreciate that those many layers and stacks have proliferated, multiplied, splintered, forked, deprecated, and been abandoned.

Indeed, interoperability and standards still matter. As such, xkcd 927 is alive and well.

Most folks agree that companies shouldn’t be “rolling their own” encryption. However, there are post-quantum encryption futures ahead that will need to be applied and made retroactive to many hundreds of zettabytes.

And with that analogy in mind, here’s to MACH succeeding. Or, as I said four (4!) years ago… imagine a world where consumer expectations are fully satisfied in the ways we expected and a delight to use.

What will be the tipping point for MACH architecture?

Place your bets…

A few readers have asked for my favorite links for the week to make a return. Allow me to happily oblige and ape my other favorite newsletter writers’ formats. 🤓

One for the road

💳 If you know, you know.

blippy.com swag

Thank you for reading

Thanks for all the reader feedback on my SXSW 2024 coverage. I also appreciate that resorting to asking your favorite Generative A.I. to summarize and get to the point is real. So, I’m keeping this post to under 1500 words. 🤖✍️

If you’d like to catch up with me to discuss, let’s chat!

Disclosure

I am linking to my disclosure.

p.s. As I’ve gotten older, I have come to appreciate getting snail mail. If you have time to drop me a postcard that would be amazing. ✉️

Topics:

11ty ackronym api backronym bpf cloudnative cms composable framepointers headless links mach mckinsey microservices npm performance redmonk rroa sentiers sre

✍️ 🤓 Edit on Github 🐙 ✍️

Share and discuss on LinkedIn or HN

  • Get Fudge Sunday each week