Share via

Hub and Spoke or Message Bus Architectures are as legacy as tape and vinyl

  • Article

Philosophy was never my strong point (although I can tell you anything you need about electrophilic reactions of osmabenzenes). 

Anyways where was I. Hub and Spoke versus Message Bus has been a long standing philosophical discussion. Well why chose one or the other when you can chose both? That's what we did with BizTalk Server 2004 taking the best of both worlds and putting them together with the specific scenario of integration in mind.  I recommend that everyone reads this document to see what I mean.

Btw. Thanks to everyone for coming along to the Belgium Launch event. We had a lot of fun and it was just fabulous to talk to so many customers using the product in cool ways.

Comments

  • Anonymous
    March 30, 2004
    'this' link appears to be broken Scott.
  • Anonymous
    March 30, 2004
    Your just too quick for me. All fixed.
  • Anonymous
    March 30, 2004
    All fixed.
  • Anonymous
    March 30, 2004
    Looks likt the URL should be: http://home.comcast.net/~sdwoodgate/BTS2004topology.doc

    Scott
  • Anonymous
    March 30, 2004
    The comment has been removed
  • Anonymous
    March 30, 2004
    After our BPELJ rant, it's time for some reality.
  • Anonymous
    March 30, 2004
    Thanks for that Scott...excellent!

    A long overdue subject of discussion. ;-)

    So basically what i understand from the document is that the notion of a 'bus' depends on whether we are talking about this from a scalability or a subscription point of view.

    I see the advantage of the flexible MessageBox architecture with the stateless Host instances.

    The scope of this 'MessageBox network' is determined by whatever can be managed within a 'BizTalk Group'. So, within the context of subscriptions, how does this 'BizTalk Group' or 'MessageBox network' work across an enterprise WAN?

    Are there any things we should be weary of (e.g. latency) if we employ a BizTalk 'Bus' (i don't want to mention ESB - whoops already did!) as an infrastructure across an Enterprise?

    Or is it a definite no-no, and we would be better to have Zonal BizTalk Groups, and all the implications that go with that from an Operational/Admin/Deployment/Routing point of view.
  • Anonymous
    March 31, 2004
    Hey Scott, what would be VERY valuable (for my Financial Services industry) would be a rich interop story for Tibco Rv & BTS2004, as RV is NOT going away at all on Wall Street. A much more effective arguement (and sales strategy) would be for a richer SOA integration story between Smart Client/WinForm Apps & TIB-RV using BTS2004...any thoughts?
  • Anonymous
    April 03, 2004
    The comment has been removed