This is a comprehensive tutorial that teaches fundamental and advanced SOA design principles, supplemented with detailed case studies and technologies used to implement SOAs in the real world. ***We'll have cover endorsements from Tom Glover, who leads IBM's Web Services Standards initiatives; Dave Keogh, Program Manager for Visual Studio Enterprise Tools at Microsoft, and Sameer Tyagi, Senior Staff Engineer, Sun Microsystems. All major software manufacturers and vendors are promoting support for SOA. As a result, every major development platform now officially supports the creation of service-oriented solutions. Parts I, II, and III cover basic and advanced SOA concepts and theory that prepare you for Parts IV and V, which provide a series of step-by-step `how to` instructions for building an SOA. Part V further contains coverage of WS-* technologies and SOA platform support provided by J2EE and .NET.
Much too verbose, will confuse someone just getting into SOA
This book has far to much `Hamburger Helper` in it. I am a veteran at SOA and wanted a book I could reference. It is long winded. For example, the author goes through 106 pages before he gets to the true definition of SOA on that page 106. This should be in the first 5 pages. The definition is good but why the heck did he have to confuse the novice reader with all that `contemporary` and `Primitive` SOA discussion. I cut through those pages fast but I bet a novice is going to be really confused reading this book. I would not recommend this to customers as some of the testimonials at the front suggest. I picked up a few ideas here and there. A two star is about right.
Thomas Erl has an easy to read writing style. Highly recommend this book.
While I agree with some of the other reviewers that this book can be 'long winded' at times, it is still a book with a lot of rich information on SOA technology. It is not a book about how to perform SOA implementation, but contains abstract problems and how SOA solves those problems. Thomas Erl is one of a few technical authors I've found to have a gift of communicating well on paper, and this book's content moves along in a graceful manner. If you are looking for a very technical implementation book on SOA then this is not the right book (though I'd look at some of the author's more recent releases for that). This is not a book to be read quickly, as the author presents the information in a 'beefy' style with a lot of information, some perhaps redundant, but I believe is there to drive home his message. As a software engineer for nearly 30 years, I've read nearly 100 technical books, but I must say that this one (my first one of Thomas Erl's Series) stands out as one of the best. SOA is a very complicated topic, and there is not a short-cut to fully digesting it. I would highly recommend this book to be part of your SOA reference library.
Independent View of SOA
Thomas Erl in this book provides an excellent reference and an independent/agnostic view of SOA that is not cluttered with Vendor speak. What I thought was valuable is the definition of business benefits, case studies and the beginning of SOA Principals and terminology that provides an organization a mechanism to organize their efforts and improve focus. Having worked with Web Services since 2001 and implemented them at many customers, the application and discussion of WS in conjunction with SOA is very helpful.
Excessively long winded for my use
It's hard to understand how the same author wrote this and SOA Principles of Service Design (The Prentice Hall Service-Oriented Computing Series from Thomas Erl) and Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services (The Prentice Hall Service-Oriented Computing Series from Thomas Erl), both of which had more useful information in a much more compact package.
The only real use I can think of for this book is perhaps to quote in a sales context regarding the benefits of SOA to someone who hasn't heard of it. That said, although I believe in SOA as a powerful mechanism, I believe the claims in the book are less well supported then the heft of the book might imply. Other technical details like the importance of UDDI are largely out of date.
I disagree with some of the other reviewers who call the book overly theoretical: I would not give it that much credit. Theory would call on or reference solid research; this book provides anecdotal evidence at best.
Aside from some potential use to sales folks (perhaps why Sun, IBM and MS endorse the book), I think most will want to pass on this one.
Too much theory
I found reading this book boring after the first 6 chapters. What would have been more interesting is the author giving possible solutions (i.e. specific products) that could meet the specifications he laid out in each chapter. This book does not give specific real-world solutions that fit the descriptions and specifications that are described as constituting a Service-Oriented Architecture. After reading this book, I understand the architecture, but could not recommend any specific products that would fit the architecture.
We does not store any files on its server. We does not reserve any rights to, nor claims copyright to, any software names listed on these pages. All references are copyright to their respective owners.