MGWC case studies

MGWC · Put your knowledge to work in context.

The MuleSoft Certified Integration Architect – Level 1 (often abbreviated MCIA Level 1, and catalogued here under the alias MGWC) is an architecture-level credential for integration practitioners who design MuleSoft-based solutions rather than only build individual flows. It suits integration architects, senior developers moving into design roles, and platform leads who own how APIs and integrations fit together across an organisation. The MGWC case studies are 5 cases and about 5,598 words.

Two legacy estates, one 14-month decommission commitment

Northwind Retail has completed its acquisition of a regional competitor. Between them they run 62 production integrations: 41 on an on-premises TIBCO BusinessWorks estate and 21 on Mule 3.9, with 240 endpoint definitions recorded in a CMDB that the operations team admits is roughly 30% stale.

980 words, about 5 min 2

Eligibility API for three channels with very different appetites

A national health insurer exposes a Member Eligibility capability to three consumers: a consumer mobile app with peaks of 400 requests per second at Monday 08:00, a provider portal expecting 99.95% monthly availability, and an overnight clearinghouse that submits 20,000 single-record queries between 01:00 and 03:00. Today a single Experience API calls a CICS mainframe region directly over HTTP Request.

1,098 words, about 5 min 3

Duplicates, a five-attempt retry, and an 800,000-message backlog

A distributor processes 1.2 million orders per day through a Mule 4 application that accepts an order over HTTPS, publishes it to an Anypoint MQ queue, and has on-premises workers consume and post to SAP ERP over HTTP. The ERP occasionally takes longer than the 30-second client timeout, and sometimes commits the order and then fails to respond; the application retries and a duplicate order is created.

1,062 words, about 5 min 4

Forty brokers, one static secret, and a PCI assessor

A payments-adjacent insurer runs a claims-status API consumed by 40 external broker agencies and by an internal claims portal. Each broker holds a static client ID and secret, all created in the production business group.

1,155 words, about 6 min 5

Eight teams, four environments, deployments from a laptop

Eight Mule teams at a logistics company deploy to Dev, QA, Stage and Prod. Three teams run on CloudHub 2.0 and five on Runtime Fabric on-premises for data-residency reasons.

1,303 words, about 7 min