I bought the book some time ago by Nicolai Josuttis "SOA in Practice", and I must say that I am reading with pleasure.
I'm interested in everything that is service-oriented architecture for several months now and I must say that I really like his approach: it is balanced, and certainly not the hosannas SOA as a panacea for all ills and definitive solution to the global problems of integration .
The definition of SOA is something elusive: google SOA across the Internet will find everything!
This is a bit 'because it is an emerging technology and a little' because it is a technical standard, but a guideline for this reason every definition is always a little 'ambiguous and poorly defined. Searching the Internet is easy to see that there are many definitions of SOA as many are those who write to us. The definition provides that
Josuttis I think is one of the best: the following.
"SOA is an architectural paradigm for dealing with business processes distributed over a (possible) large landscape of existing and new systems heterogeneus That can be under the control of different owners."
It 's interesting because in one sentence captures the salient aspects of SOA:
1) integration between heterogeneous systems and distributed
2) We speak of Business Processes, and data exchange. The SOA approach is actually business-oriented, rather than the technical integration.
Reading the book is Josuttis really interesting for someone like me, is passionate about issues of system integration: Highly recommended!
A concise explanation of SOA and alternative, but still illustrative, is given by John Reynolds at the following address:
http://weblogs.java.net/blog/johnreynolds/archive/2005/01/th
e_soa_elevato.html
I wanted to report it because when I read it, they had to respond to a series of questions that I had made and which, after days of searching, I could not find a solution.
0 comments:
Post a Comment