EAIGuide
  • Welcome to the Integration Handbook
  • The Basics
    • What Is Application Integration?
    • Types of Application Integration
      • Event-Driven Architecture (EDA)
      • B2B Integration (Business-to-Business Integration)
      • iPaaS (Integration Platform as a Service)
      • Middleware Integration
      • Data Integration
      • API-Led Integration
      • Hub-and-Spoke Integration (ESB)
      • Point to Point Integration
    • Enterprise Integration Patterns
      • Message Creation
        • Message
        • Request-Reply
        • Events
      • Message Routing
        • Pipes & Filters
        • Router
        • Splitter
        • Aggregator
        • Routing Slip
        • Scatter-Gatherer
      • Message Transformation
        • Content Enrich
        • Content Filter
        • Translator
        • Claim Check
        • Normalizer
        • Canonical Data Model
      • Message Channel
        • Send and Receive
        • Point to Point
        • Publish Subscribe
        • Invalid Message
        • Guaranteed Delivery
        • Dead Letter
        • Messaging Bridge
      • Message End Point
        • Send and Receive
        • Transactional
        • Polling
        • Event Driven
        • Dispatcher
        • Consumers
        • Durable Subscriber
        • Idempotent Receiver
      • Messaging System Management
    • Integration Center Of Excellence
      • Innovation and Agility
      • Consistency and Quality
      • Cost Savings
      • Efficiency and Speed
      • Risk Management
  • Design and Development
    • Project Human Resources
      • Integration Architect
      • Integration Developer
      • Project Manager
      • Functional SME
      • Functional Tester
      • Technical Tester
      • Training & Support
    • Process Flow Design
      • Business Process Mapping
      • Functional Design
      • Technical Design
    • Process Flow Development
      • Coding Standards
      • Naming Conventions
      • Data Preparation for Testing
      • Unit Testing
      • Integration Testing
      • Go-Live Preparation
  • Monitoring & Support
    • Maintaining Integrations
      • Monitoring Messages
      • Message Logging
      • Error Handling
      • Retrigger Messages
      • Alerting Frameworks
      • Documentation
      • Version Control
    • Continuous Improvement
      • Performance Engineering
Powered by GitBook
On this page
  • Hub
  • Spoke

Was this helpful?

  1. The Basics
  2. Types of Application Integration

Hub-and-Spoke Integration (ESB)

Advantages of a Central Hub Model

PreviousAPI-Led IntegrationNextPoint to Point Integration

Last updated 8 months ago

Was this helpful?

A hub-and-spoke model connects multiple systems (spokes) to a central hub. Central hub is also known as Enterprise Service Bus (ESB). Messages are exchanged between multiple systems via the central hub, which acts as a mediator of all messages from one central place. Rather than messages flowing from one system to another, they all go through one central hub.

Hub

Hub orchestrates all messages between systems. Its important function is to decouple the direct connection between multiple systems. This way, the systems do not have to know about the data formats and protocols of other systems.

Hub handles tasks such as message routing, transformation, enforcing business rules, security, data encryption and decryption, and other related Integration activities.

Spoke

The spokes, as individual systems in the hub-and-spoke model, are responsible for sending and receiving information from other systems. They interact with the hub to send and receive messages and do not connect to another spoke directly.

If spokes connect with each other directly, it is called .

point to point
point-to-point integration