In fact performance was always a key issue when considering SOA for business
integration. When SOA principles are applied too rigidly, you can expect some
run-time issues. Hence it is better not to go by any book or guidelines and instead, to
adopt your own SOA-based system that is scalable and reliable for your needs. The
primary factor that you need to understand is that SOA is a paradigm shift in doing
business and requires a complete comprehension of the events, processes, and fault
endpoints that occur in your enterprise.
Developing enterprise applications is much more than just building a system that
can process and share data between web services and various clients. Consider, for
example, an airlines reservation web service that processes the guest itinerary. If a
reservation cannot be made, it should have the capability of contacting a partner
airline's web service and then process the itinerary. If the itinerary processing is
successful, it should confirm the booking to the client. Now, there is more than
one type of enterprise system involved. Which part of your enterprise system will
orchestrate the transaction? Who will set the guidelines for fail-safe communication?
There is a clear need for a "middle man" or a "centralized web service" to orchestrate
these disparate web services to make the reservation process successful and failsafe.
Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25