|
|
z2003-11-10- Udell Message Bus
|
|
Whenever any Form of Government becomes destructive of these ends, it is the Right of the People to alter or to abolish it, and to institute new Government, laying its foundation on such principles and organizing its powers in such form, as to them shall seem most likely to effect their Safety and Happiness.
|
|
(backlinks off)
|
(map off)
|
(search off)
|
|
last edited
by BillSeitz
on
Jun 16, 2008 12:54 am |
Jon Udell on the use of a Message Bus architecture in a Web Services environment for Application Integration. If XML messages are the transaction currency of a service-oriented network, the argument runs, then there are going to be astronomical numbers of messages. While the messages are in flight, we'll need new kinds of dynamic message stores to index, search, monitor, and correlate them... Mc Kinsey partner, [Chris Barlow], described how [Delta Airlines] has radically reorganized its application portfolio. Point-to-point integration is out; Event Driven communication across a common message bus is in. When you build a system this way, message queues are the first and best way to take the pulse of its real-time state... [Frank Martinez] makes a crucial distinction between message data and message Meta Data. In the realm of Web Services, it's the difference between SOAP bodies and SOAP headers. The bodies eventually land in an operational Data Store, the headers often don't. Yet the headers define the ConText of the message: who (or what) is sending it and why.
Bill Seitz, fluxent at gmail dot com, Weblog