In system integration, middleware is software that sits between applications to move, transform, validate, and orchestrate data. Instead of every system calling every other system directly, middleware provides a controlled hub for mappings, credentials, and cross-cutting rules that do not belong inside either endpoint product.
Middleware is not magic and not always required. It becomes valuable as the number of systems, transformation rules, or operational requirements grows. For how the runtime behaves (retries, idempotency, quarantine), see how middleware works. For choosing hub vs point-to-point, see middleware vs direct API integration.
What middleware typically does
- Accepts events or pulls data from source systems
- Applies data mapping and validation
- Calls destination APIs in a controlled order
- Centralises credentials and environment configuration
- Gives operators one place to see flow status and failures
Deep retry, replay, and logging design belongs in the how-page; the definition here is the hub role.
When a hub is needed
Point-to-point links are fine for one simple connection. A hub earns its keep when:
- Several channels must write into one system of record (or the reverse)
- The same business event must fan out to accounting, CRM, and fulfilment
- You expect to replace one SaaS tool without rewriting every neighbour
- Finance or compliance needs consistent auditability across flows
If you only have one stable link with simple fields, direct API integration may be enough.
Middleware as a hub
- Source system emits or exposes data
- Middleware receives and authenticates
- Rules transform and enrich the payload
- Destination APIs are called as needed
- Outcomes are visible to operators
A practical multi-system example
A retailer takes orders from an online store and a POS, and must keep accounting and warehouse systems aligned. Without a hub, ecommerce posts sales one way, POS posts another, and stock adjustments are copy-pasted. With middleware, both sales channels publish a common “order confirmed” event; the hub maps each channel’s quirks, posts the customer invoice to accounting, and sends a fulfilment request to the warehouse. When the ecommerce platform is replaced later, only the channel adapter changes—the accounting and warehouse contracts stay.
Forms middleware can take
Middleware may be a dedicated iPaaS platform, a custom integration service, a message queue with workers, or an API gateway plus orchestration. The label matters less than ownership, observability, and clear contracts between systems.
Buy vs build
iPaaS tools accelerate common connectors. Custom middleware fits unusual orchestration, strict data residency, or deep domain rules. Many estates mix both. Evaluate skill availability and lock-in honestly before committing.
Anti-patterns to avoid
- Using the hub as an uncontrolled second database of conflicting truths
- Hiding pricing or tax logic so deeply that nobody can explain it
- Building new point-to-point sprawl inside the hub without shared standards
- Launching a sophisticated platform with no named owner for failures
FAQ
Does middleware replace APIs?
No. Middleware uses APIs. It organises and hardens the conversations between systems.
Is an iPaaS always middleware?
Functionally yes when it orchestrates and transforms between systems. You still need governance; a visual flow can become shadow IT without ownership.
When should we stay point-to-point?
When systems are few, mappings are simple, and you lack capacity to operate a hub. Design connectors so they can move behind a hub later if needed.
Who should own middleware?
Someone accountable for mappings, credentials, alerts, and vendor API changes—often IT with finance as process owners for money-moving flows.
How does this relate to e-invoice or compliance APIs?
A hub is useful when portal uploads, accounting documents, and submission APIs must stay consistent. See MyInvois portal vs API integration & middleware for a concrete compliance-oriented discussion.
Related concepts
Runtime detail: how middleware works. Decision guide: middleware vs direct API. Foundations: what is API integration.