This way a consumer or client application can
interact in the 'MOM way' through the ESB. Maybe we also need a simple and, again,
a standard way to find and invoke a concrete service at the ESB, matching an abstract
service interface.
Why Enterprise Service Bus
[ 20 ]
These standards are evolving and are at different stages of adoption. Similar is the
case of support for these capabilities across multiple vendors' solutions. Hence,
the tail piece is that it is time now to gather all our experience in message bus
based architectures, and leverage it to define and demonstrate service bus-based
architecture. So, how do we decide that we need an ESB-based Architecture? Read
on the next section and you will come to know.
Making the Business Case for ESB
Just like any one of you, I am not satisfied yet with enough reasons for why to use
ESB. Hence, this section is going to explain more about the value proposition ESB is
going to bring to your IT infrastructure.
There are a few concerns we need to address when we do point-to-point or a similar
style of integration:
How many channels do we need to define for complete interoperability?
How easy it is to change a system interface, while still maintaining
interoperability?
How do we accommodate a new system to the IT portfolio?
How much we can reuse system services in this topology?
Where do we plug-in system management or monitoring functionality?
Let us address these issues one by one.
Pages:
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51