- Shopping Bag ( 0 items )
Posted March 20, 2008
Very Good high level companion
This book covers the complex process of planning, designing and implementing service-oriented architectures that meet organizational goals. It is an essential companion to any software developer, architect, or project manager implementing-or thinking about implementing-a service-oriented architecture.Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.
Posted February 8, 2006
SOA is a lot of work, but worth it
Building SOA is all about doing the right things during the planning and analysis stages and the building on top of that foundation. That is a key thing I learned by reading this book - that and of course all of the things our company needs to specifically do to actually build the services. SOA is not revolutionary in my opinion, but it does shake things up quite a lot. It's all for the best, however. The benefits you are working toward when you invest in SOA are very attractive. After fully understanding what this platform is all about I can truly see why we should go ahead with some of the plans we've been mulling over. I was very impressed with the writing and the consistency with which this author introduces subjects and then builds on them, layer by layer with each subsequent chapter. This is a real tutorial on a very big subject matter and it does a great job of providing instruction and a lot of practical guidance.Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.
Posted August 24, 2005
A lot to cover
It's a serious challenge to develop in SOA if you have never done this before. The field is still developing rapidly. Plus SOA has by now subsumed many standards or specifications. The totality of which is daunting to assimilate. Erl does a formidable job in helping you overcome these obstacles. In essence, he shows that SOA has 3 main parts - a service, its description, and messages that pass between services. Where a service encapsulates a piece of logic that is meant to be modular and reusable. This per se is really little different from subroutines, which have been with us since Fortran and Algol. After all, think of all those massive Fortran libraries that have been built up for scientific and engineering uses. But with SOA, a key difference is that the parts or players are inherently distributed over a network. Unlike the monolithic Fortran executables. The book shows that SOA potentially lets you build a loosely coupled, distributed system. Where the messages and descriptions play the pivotal part in enabling this. And these rest on XML, as the base technology. You should be versed in XML prior to commencing this book, especially with the usage of XML namespaces in defining terms. Also, if any of you have had experience in writing client-server programs, using Remote Procedure Calls, then the loose coupling of SOA can be attractive. RPCs invariably led to a tightly coupled system that was often hard to maintain and modify.Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.
Posted March 17, 2009
No text was provided for this review.