Path: SOLID in MuleSoft · Part 6 of 6
DIP is not externalised configuration. It is the business flow defining the model it needs and adapters conforming to it — shown in Mule 4 with swappable ERP and in-memory implementations.
Path: SOLID in MuleSoft · Part 5 of 6
One order endpoint that returns everything to everyone, split into consumer-shaped interfaces — and why the strongest argument for ISP in integration is data exposure.
Path: SOLID in MuleSoft · Part 4 of 6
Mule has no inheritance, but LSP still bites: two adapters behind one contract, where the new one keeps the field names and quietly changes their meaning.
Path: SOLID in MuleSoft · Part 3 of 6
Adding a payment method to a Mule 4 app without touching the router — with config-driven dynamic routing, MUnit evidence, and an honest look at the trade-offs.
Path: SOLID in MuleSoft · Part 1 of 6
A code-backed look at the five SOLID principles in Mule 4 — where each one fits integration work, where it needs translating, and where it stops being useful.
Path: SOLID in MuleSoft · Part 2 of 6
SRP is not about small flows. It is about grouping logic by the reason it changes — shown with a Mule 4 order flow before and after, with MUnit tests.
