htshozawa wrote: > > > Hi Patrick, nice to hear from someone new! > > --- In [email protected] > <mailto:service-orientated-architecture%40yahoogroups.com>, Patrick May > <[EMAIL PROTECTED]> wrote: > > > > The one functional area in which typical ESBs do not overlap grid > > platforms is the ability to transform various object formats. Once > > information is mapped from the source formats into a common model > > (often an OO model, which is why "data grid" is a misnomer), the > > publish/subscribe or queueing transport layer most often provided with > > an ESB is pretty limited. > > +1. ESB may be used to convert from/to a specific format-transport > to a common model. Another situation is when a grid is a overkill.
A grid is never overkill! It is THE singular programming model that allows for infinite expansion and scalability. It also is the most plugable architecture because you can change processing around, in real-time by deploying "changed" processing units, independent of the rest of the system. ESBs are single file pipe lines that require in-place replacement and rewiring wheres as grid processing units can be swapped in and out and change the system flow dynamically without any other participant seeing the physical changes. Gregg Wonderly
