So, whereas in the pre-ESB world, we have been using
CORBA IDL (Interface Definition Language), or Tuxedo FML (Field Manipulation
Language), or COM/DCOM Microsoft IDL, and CICS common Area (COMMAREA)
as the service definition language, we now use WSDL as the interface in
standard-based ESB architectures.
Maturity and Industry Adoption
Having looked at a few of the similarities and differences between service bus and
message bus, it is time now to look at realities which exist in the industry today. We
agreed that an ESB can do lot many things, and for that matter a message bus can
too. We then talked about the differences a service bus has to offer.
How mature is the technology today to address these differences? Have we started
practical implementations of service bus in a big way yet? The answer to this
question is neither yes nor no. The reason is that necessity runs before standards.
Rather, when you agree that you need description and discovery along with other
features for a service bus-based architectures, the question is, will the existing
standards like Universal Description Discovery and Integration (UDDI) alone will
help to achieve this? Maybe we need a simple and standard way to specify a pair of
request-reply queues along with a HTTP URL (mechanism to specify HTTP URL is
already available) in the WSDL itself.
Pages:
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50