I managed to slog through 250 pages of this 800+ page book before giving up in despair. I have read other books on design patterns, domain-driven design and software architecture but I honestly could not understand what new contribution -if any- the patterns included in this book make.
I agree with some other Goodreads and Amazon reviewers of this book in finding it verbose and bloated, buzzword-ridden, saturated with too many diagrams of doubtful or no value and that not even its case studies manage to ground it and make it intelligible.
My recommendation is that if you are new to service-oriented architecture, give this book a wide berth.
Much better than Erl's Service Oriented Architecture, but Erl still has a penchant for repetition, resulting in a bloated book. And the "case studies" don't add much insight. The book does serve a purpose of most patterns books in naming the patterns and providing for a common terminology. I'm moving on to SOA in Practice, which is already much more concrete in just the opening chapters.
Note: Read on Kindle DX, text was well formatted but many of the diagrams were difficult to understand since there is a heavy reliance on color-coding of the diagram blocks. This is not a big loss, the diagrams did not add a lot. However, PC and iPhone Kindle software do present the diagrams in color when needed.
The patterns are logically grouped and I enjoyed the quick info headings that display the specific application and impacts of implementation. While I appreciated the very thorough approach that Erl (et al) took in composing the pattern reference sections and example use cases, I found this book to be somewhat weighted down by the overuse of diagrams. Overall, I think it is a great resource and a fine companion to David Chappell's Enterprise Service Bus.