The bus is just the intermediary. If you think of the internet then DNS
is in effect the sort of Bus I mean.
I see what you mean. I believe our vision of what a bus is, differ.
________________________________
From: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of
Steve Jones
Sent: Wednesday, March 28, 2007 11:16 AM
To: [email protected]
Subject: Re: [service-orientated-architecture] ESB Standard
Definition
How do you mean what do we do? The Bus has 6 services on it,
this means that any off bus application server or environment can
consume those services and create services or applications of their own.
If for instance this off bus application does a bunch of co-ordination
(might even use a process engine) then its still an application in the
same way as any other. If that new application is actually a set of
newly developed services then these are exposed back into the bus.
The bus is just the intermediary. If you think of the internet
then DNS is in effect the sort of Bus I mean.
On 28/03/07, Bill Barr <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> > wrote:
To me you've just said that ESB = Application
Development. JBI does a good job of standardising how products are
plugged together from an IT infrastructure perspective, but I wouldn't
say its an ESB as its focus is on connecting engines and not on
connecting services.
Is there a way of avoiding this?
Let's assume a bus, per your description. Let's attach 6
services to it. Now what do we do?
--
email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
phone: 425.679.3533