I write about what happens between systems: APIs, MuleSoft integrations, delivery pipelines and, more and more, working with AI agents. I like to take an idea everyone repeats, such as SOLID, retries or GitFlow, and see what is left of it once it meets a real Mule application.
From branching strategy to CloudHub 2.0 deployment: GitFlow, Maven versioning, pipeline templates and approvals, in that order.
4 articles · Start reading →
An introduction and five principles applied to MuleSoft integrations, with before-and-after examples and MUnit tests.
6 articles · Start reading →
Scatter-Gather, Choice, For Each and the Anypoint MQ dead letter queue come from the book Enterprise Integration Patterns. Knowing the name of the pattern shows the problem the component solves, what it costs and when you can do without it.
A folder in your vault becomes the blog. The note's name becomes the address, the top of the note becomes the page, and the site refuses anything that is wrong. Free, with a ready-made Astro template.
A short request, a Mule 4 API and OpenSpec show how a spec reviewed before any code reveals what the request forgot and catches a breaking change.
What the research says about AI and software development, and why I think fundamentals and review are still the job.
A plausible 200 response, an inactive customer and the rule missing from the requirement.
Retry alone turns a degraded backend into an integration outage. A public, measured, tested plugin shows the difference — and what changes once you add replicas on CloudHub 2.0.
