Hub and spoke versus bus architecture

Hub and spoke versus bus architecture

What is the major difference between hub and spoke architecture and bus architecture? What are the main pain points of each of them?

    Requires Free Membership to View

    Login

    When you register, you'll begin receiving targeted emails from my team of award-winning writers. Our goal is to keep you informed on recent service-oriented architecture (SOA) and SOA-related topics such as integration, governance, Web services, Cloud and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSOA.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSOA.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

A bus acts more like "e-mail on steroids" fascilitating point-to-point messaging with guaranteed delivery. Hub and spoke generally implies content directed rules for many-to-one communication, including idioms such as pub/sub.

This was first published in March 2003

Back to top