Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your email address or mobile phone number.
Service Design Patterns: Fundamental Design Solutions for SOAP/WSDL and RESTful Web Services 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Featured Functional Programming Titles
Check out these featured titles from O'Reilly Media and distributed publishers.
Frequently Bought Together
Customers Who Bought This Item Also Bought
Top Customer Reviews
One of the things I liked seeing was that the author does not think web services are a silver bullet. Right off the bat he warns that web services should be reserved for situations which out-of-process and cross-machine calls "make sense".
The book is broken down into seven chapters, an appendix, and a nice glossary. The chapters include From Objects to Web Services, Web Service API Styles, Client-Service Interactions, Request and Response Management, Web Service Implementation Styles, Web Service Infrastructures, Web Service Evolution, and an appendix Reference to External Patterns.
I felt the book worked at the right level of abstraction digging into details when needed to shed a deeper light on the subject at hand.
Each chapter contains several related patterns. Each pattern answers a primary question. For example chapter one Web Service API Styles cover the following 3 patterns that answer the question that follows below.
RPC API - How can clients execute remote procedures over HTTP?
Message API - How can clients send commands, notifications, or other information to remote systems over HTTP while avoiding direct coupling to remote procedures?
Resource API - How can a client manipulate data managed by a remote system, avoid direct coupling to remote procedures, and minimize the need for domain-specific APIs?Read more ›
In the pages of the very first chapter this book challenges your standard thought on Service Architecture. Over the years I have asked many colleagues why they think SOA is a superior architecture. Often I have received the response that it reduces complexity, provides loose coupling, and is the most reliable way to allow disparate systems to communicate. Naturally, the next question is, well how are those objectives met? That question tends to put a wrinkle on the face of some of the most seasoned software architects. This book presents those questions, and paints candid responses before you get to page 10.
As you advance through the chapters, the author did a great job at codifying various approaches to web service design in a way that's not specific to any particular technology or specification. The pattern descriptions are easy to read, help the reader understand how to choose between them and the contexts in which to use them. The book provides an easy to reference handbook that classifies the patterns into categories that really make sense, and I think it gives practitioners a very useful vocabulary. Although the title says it's about creating services for SOAP/WSDL and REST, it's not a book about either.Read more ›
When I saw this book on the Amazon, I purchased the printed book straight away without having had a quick read of the book, say from a pdf you can download on the Internet, since I really enjoyed reading the other two pattern books in the Martin Fowler series, i.e., Patterns of Enterprise Application Architecture (PoEAA) and Enterprise Integration Patterns (EIP).
It turns out to be a disappointment with this book.
Why? First, with the other two patterns books, in some cases I learned/relearned some core concepts of Enterprise Application or Enterprise Integration, while in other cases I learned some best way to describe what I had already learned from experience. Unfortunately, That has not been the case with this book about SOAP based Web service or REST Web service, except "situations in which out-of-process and cross-machine calls 'make sense'" (page 8).
Second, the patterns in the book generally try to prescribe what industry has been actually doing (often using a different vocabulary). The problem starts when you try to have a more clear understanding of the patterns by reading the examples for the patterns and by trying to make a connection between the patterns and actual SOAP or REST implementation technologies.
Take chapter 2 Web Service API patterns as an example.Read more ›
Most Recent Customer Reviews
One of the most influential architecture books of the early 00s was Enterprise Integration Patterns by Gregor Hohpe and Bobby Woolf. Read morePublished 11 months ago by Andrew Johnston
This book provides a deep dive into web services: their foundational concepts, their architecture, and a taxonomy of the important problems and the patterns which solve them. Read morePublished 22 months ago by Dan Hermes
I purchased this book from Amazon last year and I had the opportunity to hear the author speak twice on this subject. His talks, as well as this book, are highly recommended. Read morePublished on April 1, 2014 by Robert Hurlbut
After attending one of Rob's presentations I decided to add his book to my collection. (Or, rather, to my Safari reading list... sorry Amazon. Read morePublished on March 25, 2014 by David P. Donahue
This book should be on your shelf if you are someone who is architecting enterprise systems. The book is language agnostic and gives theoretical advice on how to address common... Read morePublished on March 25, 2014 by William Schreiber
In my opinion, index structure and writting style makes this book unfriendly to reader ... i have nothing more to sayPublished on March 22, 2014 by Rafael BC
There's a fair amount of discussion on the SOAP/WSDL topic, but very little practical information that isnt obvious. Read morePublished on January 5, 2014 by The Wizard of Oz