Field notes on integration, architecture, and the business decisions behind them. Each entry starts with a symptom a CTO will recognize, and ends with an architecture decision you can explain in five minutes. No feature lists. No hype.
Real-time events flowing into Salesforce through three MuleSoft layers, with a nightly batch reconciling against an external API. The Experience-Process-System pattern is documented everywhere — which design decisions actually hold up in production is not.
Read the articleWhen sales sells on CRM data and operations delivers from ERP, the same movie plays out every week. Diagnosis, root cause, and what a MuleSoft middleware layer really does.
"Single Source of Truth" appears in every consulting proposal, every vendor demo, every trend article. Worth separating from the noise: what it really means, when Salesforce is the right home for it — and when it isn't.
The conversation starts the same way: "we have twenty integrations in API Connect, in an eight-year-old ESB, or in home-grown scripts, and we want to move them to MuleSoft." Below that lives a question almost no one asks: how to migrate without operations noticing.
This notebook is written from real projects. If any of these diagnoses sound familiar, it probably deserves a thirty-minute conversation.