ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

Modern B2B integration architecture: 2026

Four architectural styles dominate B2B integration in 2026: legacy hub-and-spoke, the 2000s ESB, cloud iPaaS, and event-driven mesh. Each keeps relevance on a perimeter — here is how to choose without dogmatism.

Why talk about integration architecture?

Beyond format choice (EDIFACT vs UBL), transport (AS2 vs AS4) and channel (PEPPOL vs bilateral), it remains to decide how the organisation orients its internal flows. That is what integration architecture means. Structuring choices — where mappers live, how events flow, who orchestrates sagas — determine the maintainability and scalability of the system for the next 10 years.

Hub-and-spoke legacy

Hub-and-spoke is the oldest of modern styles. A central hub (typically a dedicated EDI mapper) receives all inbound messages, transforms them to the internal canonical format, and distributes them to consumer applications via point-to-point connectors. For outbound flows, the hub serialises from internal format to the partner's expected format.

Strengths: conceptual simplicity, centralised governance, reusable mappers. Limits: single point of failure, expensive vertical scaling, the hub becomes an operational bottleneck as flows multiply.

Iconic products: Axway B2Bi, OpenText Trading Grid, IBM Sterling B2B Integrator. These products are 20-25 years old, mature, and still massively deployed in large organisations in 2026.

ESB — Enterprise Service Bus

The ESB emerged in the 2000s (term popularised by Roy Schulte of Gartner) to extend hub-and-spoke to all application integrations — not only EDI. The core idea: every flow transits through a central bus that orchestrates, transforms and routes.

Strengths: universal protocol support (HTTP, JMS, FTP, AS2), XSLT or DataMapper transformation, BPEL or BPMN orchestration. Limits: over-centralised, monolithic deployments, heavy vertical scaling, central discovery prone to team conflicts.

Iconic products: TIBCO BusinessWorks, IBM Integration Bus (formerly WebSphere Message Broker), Oracle Service Bus, MuleSoft Anypoint (before its iPaaS pivot). In 2026, many ESB deployments are in progressive decommissioning, replaced by iPaaS or event-driven.

iPaaS — Integration Platform as a Service

The iPaaS is the cloud evolution of the ESB. Architectural principles remain close (hub, transformations, orchestration), but infrastructure is managed by a cloud provider, and the interface is typically visual (drag-and-drop) rather than developer-oriented.

Strengths: instant deployment, managed horizontal scaling, pre-built partner connector marketplace (SAP, Salesforce, Workday, NetSuite…), accessibility to non-developer profiles (business analysts). Limits: vendor lock-in, variable costs on volume, limited control on infrastructure SLAs, sometimes opaque debugging.

Iconic 2026 products: Boomi, Workato, Celigo, MuleSoft Anypoint cloud, SAP Integration Suite, Microsoft Azure Logic Apps, Tray.io. For EDI flows specifically: Stedi (API-first), Pagero, Tradeshift, ediCom, Comarch.

Event-driven mesh

The event-driven mesh is the most recent architecture. Instead of a central hub, a distributed event bus (typically Kafka, Pulsar or NATS) is adopted where each system produces and consumes events asynchronously. Transformations are operated by specialised consumers (microservices), not by a central hub.

Strengths: native horizontal scaling, maximal system decoupling, event replay possible (event sourcing), resilience to individual failures. Limits: steep learning curve, complex distributed observability, per-partition ordering guarantees, eventual consistency.

This anchoring suits particularly organisations that have already committed to microservices. For EDI flows, the event-driven mesh typically appears in second-generation hubs: the PEPPOL access point emits an INVOICE_RECEIVED event on Kafka, several consumers (accounting, management control, payment, archival) process it independently.

Iconic tools: Apache Kafka + Connect, Confluent Cloud, AWS MSK, Apache Pulsar, NATS, Redpanda. On EDI saga orchestration: Temporal and Camunda.

Choosing among the four

No style is universally superior. The right reflex is to match style to context:

  • Legacy hub-and-spoke remains relevant for organisations with stable EDI volume, known partners, and centralised governance. Do not replace for the sake of replacement.
  • ESB still makes sense when migrating from a multi-application legacy, but no new project should start ESB in 2026. Prefer iPaaS for ESB-like new projects.
  • iPaaS is the default choice for new B2B integrations, especially for organisations with few internal integration teams. The connector marketplace amortises the initial investment strongly.
  • Event-driven mesh wins for organisations with high volume, strong system heterogeneity, and established microservices culture. Not the right starter if the team lacks experience.

Further reading