<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://merolhack.github.io/mach-playbook/</id><title>MACH Playbook</title><subtitle>Practical guides and patterns for Microservices, API-first, Cloud-native, and Headless architecture.</subtitle> <updated>2026-04-05T13:22:24-06:00</updated> <author> <name>merolhack</name> <uri>https://merolhack.github.io/mach-playbook/</uri> </author><link rel="self" type="application/atom+xml" href="https://merolhack.github.io/mach-playbook/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://merolhack.github.io/mach-playbook/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 merolhack </rights> <icon>/mach-playbook/assets/img/favicons/favicon.ico</icon> <logo>/mach-playbook/assets/img/favicons/favicon-96x96.png</logo> <entry><title>When NOT to Use Microservices: A Decision Framework</title><link href="https://merolhack.github.io/mach-playbook/posts/when-not-to-use-microservices-a-decision-framework/" rel="alternate" type="text/html" title="When NOT to Use Microservices: A Decision Framework" /><published>2026-04-04T00:00:00-06:00</published> <updated>2026-04-05T10:42:12-06:00</updated> <id>https://merolhack.github.io/mach-playbook/posts/when-not-to-use-microservices-a-decision-framework/</id> <content type="text/html" src="https://merolhack.github.io/mach-playbook/posts/when-not-to-use-microservices-a-decision-framework/" /> <author> <name>merolhack</name> </author> <category term="guides" /> <summary>The honest counterweight to MACH advocacy. Microservices are not a default — they are a trade-off. This post gives a concrete framework for deciding when a modular monolith is the right call. The Cost Nobody Talks About in Conference Talks Network latency, distributed debugging, data consistency across boundaries, operational overhead per service, and the cognitive load on every engineer who ...</summary> </entry> <entry><title>Video Review: Reacting to Netflix’s Architecture — What We Can Learn and What Doesn’t Apply</title><link href="https://merolhack.github.io/mach-playbook/posts/video-review-reacting-to-netflixs-architecture-what-we-can-learn-and-what-doesnt-apply/" rel="alternate" type="text/html" title="Video Review: Reacting to Netflix’s Architecture — What We Can Learn and What Doesn’t Apply" /><published>2026-04-04T00:00:00-06:00</published> <updated>2026-04-05T10:42:12-06:00</updated> <id>https://merolhack.github.io/mach-playbook/posts/video-review-reacting-to-netflixs-architecture-what-we-can-learn-and-what-doesnt-apply/</id> <content type="text/html" src="https://merolhack.github.io/mach-playbook/posts/video-review-reacting-to-netflixs-architecture-what-we-can-learn-and-what-doesnt-apply/" /> <author> <name>merolhack</name> </author> <category term="patterns" /> <summary>Netflix’s architecture is cited constantly as a microservices role model. This post gives a critical reading: what genuinely applies to other organizations, and what is specific to Netflix’s scale and engineering culture.</summary> </entry> <entry><title>Video Review: Martin Fowler on Microservices — Key Takeaways</title><link href="https://merolhack.github.io/mach-playbook/posts/video-review-martin-fowler-on-microservices-key-takeaways/" rel="alternate" type="text/html" title="Video Review: Martin Fowler on Microservices — Key Takeaways" /><published>2026-04-04T00:00:00-06:00</published> <updated>2026-04-05T10:42:12-06:00</updated> <id>https://merolhack.github.io/mach-playbook/posts/video-review-martin-fowler-on-microservices-key-takeaways/</id> <content type="text/html" src="https://merolhack.github.io/mach-playbook/posts/video-review-martin-fowler-on-microservices-key-takeaways/" /> <author> <name>merolhack</name> </author> <category term="guides" /> <summary>Martin Fowler’s talks are required reading for anyone serious about microservices. This post distills the core ideas, adds commentary from real-world application, and highlights what has aged well and what hasn’t.</summary> </entry> <entry><title>Video Review: Configuring Your Service Mesh — Gateway API and Routing in Practice</title><link href="https://merolhack.github.io/mach-playbook/posts/video-review-configuring-your-service-mesh-gateway-api-and-routing-in-practice/" rel="alternate" type="text/html" title="Video Review: Configuring Your Service Mesh — Gateway API and Routing in Practice" /><published>2026-04-04T00:00:00-06:00</published> <updated>2026-04-05T10:42:12-06:00</updated> <id>https://merolhack.github.io/mach-playbook/posts/video-review-configuring-your-service-mesh-gateway-api-and-routing-in-practice/</id> <content type="text/html" src="https://merolhack.github.io/mach-playbook/posts/video-review-configuring-your-service-mesh-gateway-api-and-routing-in-practice/" /> <author> <name>merolhack</name> </author> <category term="patterns" /> <summary>Service mesh configuration is where good theory meets painful practice. This post reviews KubeCon tutorials on Gateway API and service mesh routing, extracting the parts that matter for a typical MACH deployment.</summary> </entry> <entry><title>Understanding Headless CMS: Decoupling Content from Presentation</title><link href="https://merolhack.github.io/mach-playbook/posts/understanding-headless-cms-decoupling-content-from-presentation/" rel="alternate" type="text/html" title="Understanding Headless CMS: Decoupling Content from Presentation" /><published>2026-04-04T00:00:00-06:00</published> <updated>2026-04-05T10:42:12-06:00</updated> <id>https://merolhack.github.io/mach-playbook/posts/understanding-headless-cms-decoupling-content-from-presentation/</id> <content type="text/html" src="https://merolhack.github.io/mach-playbook/posts/understanding-headless-cms-decoupling-content-from-presentation/" /> <author> <name>merolhack</name> </author> <category term="guides" /> <summary>The H in MACH is frequently the least understood. This post explains why separating content storage from rendering unlocks omnichannel delivery and what tradeoffs it introduces.</summary> </entry> </feed>
