The document discusses MACH architecture, which includes microservices, API-first, cloud-native, and headless technologies for modern web development. It highlights the benefits of MACH, such as modular design, flexibility, and reduced vendor lock-in, while also addressing potential challenges like complexity and integration difficulties. The piece emphasizes the future of web development aligning with MACH principles and notes the establishment of certification standards to identify compliant services.

1. MACH based Website
Development in Minutes
Brian McKeiver

3. Co-Owner, Solution Architect
• Microsoft MVP
(Azure Cloud Native & AI)
• Kentico MVP (traditional CMS)
• Kontent.ai MVP (headless CMS)
About Me
@mcbeev
linkedin.com/in/brianmckeiver

4. Website Development
many varied paths we travel
Kinda like… What’s your favorite color?

5. Monolithic Builds
Single Page Apps
Content Management
Systems
Fully Custom
Static Site Generators
Server Side Rendering
E-commerce Platforms
Low code / no code

6. Standard Approach Challenges
 Large and complex.
 Have performance issues.
 Difficult to scale.
 Don’t take full advantage of the cloud.
 Vendor lock in.
 Slow to adopt new tech.
 Maintenance over time becomes daunting.
 Typically are Tightly coupled.

8. “ How do we keep up with
pace of change in technology
and our solutions”
… especially in the Enterprise

9. Presenting a Solution
A different approach

10. M A C H
Microservices API-first Cloud-native Headless

11. •Microservices
Individual pieces of business functionality that are independently
developed, deployed, and managed.
•API-First
Built with APIs from the ground up. All functionality is exposed via API.
•Cloud-Native SaaS
Software-as-a-Services that leverage the full capabilities of the cloud,
hosting, including elastic scaling of highly available resources. Services
are updated automatically, no manual effort required.
•Headless
Front-end presentation is completely decoupled from backend logic.
Designed to be channel, programming language, and framework agnostic.

12. Commerce example

13. MACH Advantages vs. the Past
Modular Design Benefits Fits Companies that
Easy to integrate / add
/ remove tools from
your stack.
• Best of Breed Tools
• Less Vendor Lock in
• Evolve over time, no re-platform
• Have large investments in systems
• Lots of APIs already
• Existing architecture that has multiple
platforms
Supports Innovation
Built natively with
modern tools, MACH
solutions are highly
flexible and adaptable.
• Work with what you like
• Leverage out of the box without
being limited by the box
• Power unique customer
experiences
• Have access to proficient development
talent (partner and in-house)
• Need digital solutions to be a
competitive differentiator
Modern Architecture
MACH fully leverages
advancements in
cloud and API design
• Highly performant, fast, and
available
• Continuous rolling upgrades and
new features from SaaS providers
• Experience peaks during live events or
holidays that need scalable infra
• Have business success that requires
digital
• Have Global market needs

15. • Created by a four companies originally in June 2020.
• As of July 2024, now has 111 members.
• Actively seeks software vendors, systems integrators, agencies,
consultancies, and individuals who share their vision for open and
best-of-breed enterprise technology ecosystems.
• Established certification standards that help identify those that
embrace MACH philosophies and offer MACH-certified services.

18. Microservices
An evolution of Service-orientated Architecture

19. Microservice Microservice Microservice Microservice

21. Microservices
• Order, Packaging, Shipping, and Notification in the graphic.
• Other microservices use cases could be:
• Media content: image assets and videos can be stored in a scalable
storage system and served directly to website or apps (cdn).
• Transactions and invoices: Payment processing and ordering can be
separated as independent services, so payments continue to be
accepted even if there is a service disruption with invoicing.
• Data processing: Extend cloud support for existing modular data
processing (think reporting / data warehouse).

22. Beware of the Microservice Trap

23. Api-first
Not just a “page”

24. Not API-first

27. Cloud-native
To the cloud!

28. Hosting Platforms
• Auto-scale without human
intervention.
• Meet spikes and lows in
demands.
• Pricing based on what you
consume.
• Uptime is guaranteed.
• Global in reach.
Azure Static
Web Apps

29. Azure AI Search

30. Those Tricky Vendors
• Cloud-native solutions are not just “uploaded” in the cloud.
• When they say Private Cloud == Public Cloud.
• “Kubernetes”. Just because Kubernetes is cloud-native, doesn’t
mean your vendor’s app uses containers to scale.
• Which actual databases are used in the cloud-native solution.
• Typically the solutions should be Serverless.
• You should be saving on pricing.

31. Demo: Build a MACH Site

32. Headless

33. TRADITIONAL DECOUPLED HEADLESS

34. My Headless CMS of choice
The industry’s first AI-powered CMS can help
you increase content velocity, reduce brand
risk, and drive meaningful improvements in
content ROI.

38. Headless Delivery API

40. Demo 2: Build another MACH Site

41. Who is Doing MACH Today?
Examples of real-world usage

42. MACH Brands

44. So GO! Run home!
Re-write everything into MACH!

46. MACH is great, but…
 It can get complicated fast.
 It can get expensive.
 Troubleshooting can be a pain.
 Integrations can be challenging.
 Admin / back-office experience.
 Admin / back-office SSO / roles / permissions.
 Data privacy/security (GDPR requests) can get crazy.

48. My Believe + Others
• “I think composable solutions built with MACH principles is the
future of web development architecture” – Brian.
• "By 2027, at least 60% of new B2C and B2B digital commerce
solutions, developed for the cloud, will be aligned with MACH
architecture principles". – Gartner.
• “By the end of 2024, 70% of large and medium-sized
enterprises will have composability as a key criteria for new
application planning.” – Gartner.

49. MACH Best Practices
• Minimize direct access to
vendor APIs (use your own
domain aware layer).
• Change will happen (plan, but
don’t over architect it).
• Cache all the things (even when
the vendor says not needed).
• Expect errors to happen
(always be logging globally).
• Custom business logic
belongs to you (implement
service with APIs, not code into
one single app or platform).
• Use standard architecture
principles (KISS, DRY, SOLID).
• Avoid over-use of microservice
architecture.
• Transform proprietary vendor
JSON formats (to your models).
• Use Secure API options (even
though non-secure may be offered,
use those headers!).
• View as Admin user!

50. Try it yourself
• Get Started with MACH
• Jamstack Themes
• Kontent.ai
• MACH Alliance
• rideMACH
• Azure Static Web apps + Next.js starter

51. Modular Design Benefits Fits Companies that
Easy to integrate / add
/ remove tools from
your stack.
• Best of Breed Tools
• Less Vendor Lock in
• Evolve over time, no re-platform
• Have large investments in systems
• Lots of APIs already
• Existing architecture that has multiple
platforms
Supports Innovation
Built natively with
modern tools, MACH
solutions are highly
flexible and adaptable.
• Work with what you like
• Leverage out of the box without
being limited by the box
• Power unique customer
experiences
• Have access to proficient development
talent (partner and in-house)
• Need digital solutions to be a
competitive differentiator
Modern Architecture
MACH fully leverages
advancements in
cloud and API design
• Highly performant, fast, and
available
• Continuous rolling upgrades and
new features from SaaS providers
• Less spin-up time for developers
• Experience peaks during live events or
holidays that need scalable infra
• Have business success that requires
digital
• Have Global market needs

52. Don’t Forget
• Join THAT In Slack Or Discord
• Visit the sponsors and say thanks
• Embrace the “Hallway Track”

53. Questions?

54. Thank you!
Subscribe
@mcbeev
linkedin.com/in/brianmckeiver
MACH based Website
Development in Minutes