Loading…
Case Study · 2026 – ongoing
builure is delivering, in partnership, the MuleSoft integration layer that connects an Australian general insurer's policy platform with a third-party broker rating exchange - bidirectional, multi-pattern, session-coherent across two enterprise estates.
№ 01 · The challenge
Both needed new data and new integrations.
Both directions must coexist on the same session.
Complex data transformation and modifications across every flow.
A broker session spans multiple API calls and must stay coherent from start to finish.
OAuth tokens must be brokered separately, with no token leakage across boundaries.
API-led design with an API gateway fronting the inbound callbacks.
Failures need consistent handling and a clear notification path back to the broker.
№ 02 · Solution architecture
System APIs front each estate behind a stable contract, so consumers stay decoupled from the underlying systems and new channels reuse the same layer.
Outbound and inbound traffic are deployed as distinct Mule applications, giving each a single responsibility and an independent release cadence.
API policies - rate limiting, token validation, client-ID enforcement - are applied at the gateway rather than inside the flows.
Client-credentials flows are brokered per boundary, with tokens cached and reused so identity providers aren't called on every request.
MuleSoft Object Store holds short-lived session state so a multi-call broker journey stays coherent from start to finish.
Managed Mule runtimes on Anypoint Platform, with horizontal scaling and blue-green deployment for zero-downtime cutovers.
A single error strategy returns canonical responses, correlation IDs are propagated end-to-end, and transient failures are retried before escalation.
№ 03 · Integration streams
The policy platform requests the next action from the rating exchange mid-session. The response is cached for the steps that follow.
Once the broker finishes in the rating UI, the final policy state is sent back to the exchange.
The exchange notifies the policy platform that a broker session has completed, and the platform is updated accordingly.
The exchange requests supporting data from the policy platform through the same inbound entry point.
№ 04 · Integration patterns
| Pattern | Use cases | Key features |
|---|---|---|
| Synchronous request/response with protocol mediation | Outbound queries and updates Message transformation between formats, token reuse within a session | Message transformation between formats, token reuse within a session |
| Server-initiated callback | Inbound completion and data requests Terminated and authenticated at the gateway before reaching the integration layer | Terminated and authenticated at the gateway before reaching the integration layer |
| Persistent session cache | Multi-step broker journeys MuleSoft Object Store holding short-lived session state | MuleSoft Object Store holding short-lived session state |
| Bidirectional format mediation | All flows Schema-driven DataWeave transformations | Schema-driven DataWeave transformations |
| Resilient retry | Transient downstream failures Retry with backoff, notification when retries are exhausted | Retry with backoff, notification when retries are exhausted |
| Sub-operation dispatch | Multi-phase operations A single endpoint routes to the appropriate downstream operation | A single endpoint routes to the appropriate downstream operation |
№ 05 · Engineering standards
API-led design with a clear System API stereotype on each Mule application.
A global error strategy returning canonical response envelopes across all flows.
Correlation IDs propagated end-to-end across every gateway and downstream system.
Token caching to avoid identity-provider round-trips on every call.
Configuration externalised per environment across the delivery pipeline.
Rate limiting and token validation enforced at the API gateway.
MUnit coverage plus contract testing in CI; blue-green deployments to remove downtime risk on production cutovers.
№ 06 · Tech stack
№ 07 · Closing
builure is delivering, in partnership, the MuleSoft integration layer that connects an Australian general insurer's policy platform with a third-party broker rating exchange - a bidirectional, multi-pattern, multi-auth-domain integration that keeps broker sessions coherent end-to-end across two enterprise estates.
Delivered by · Team builure
Got a similar integration ahead?
We've delivered this pattern before, and we'd like to deliver yours.