Designing event-driven architectures with Anypoint MQ
Async workflows are easy to build and hard to debug. A few patterns keep event-driven systems on Anypoint MQ observable and recoverable instead of mysterious.
Design for the messages you will lose
Assume delivery will sometimes fail and sometimes duplicate. Idempotency keys make replays safe, and a sane dead-letter policy turns a silent failure into a visible queue you can act on.
For most teams, at least once delivery with idempotent consumers beats chasing exactly once. It is simpler to reason about and it fails in ways you can see.
More from the FlorenceNext team
General22 Apr 2026FlorenceNext TeamMeet us at MuleSoft Connect EMEA: booth 24
Three talks, one live demo, and an open invite to swing by and ask awkward questions about your integration roadmap.
- Tech15 Apr 2026FlorenceNext Team
Anypoint on Azure: what changes (and what doesn’t)
A practical walk-through of the deployment story when your Anypoint runtime fabric lives in Azure rather than CloudHub.
Tech08 Apr 2026FlorenceNext TeamKong vs MuleSoft API Gateway: when to use what (and when to use both)
A practitioner's comparison from a year of running both in production. Less of a winner-takes-all than the marketing implies.