Web Services Patterns: Java Edition
March 21, 2010 by Ca-Mi.com
Filed under Web Services Books
Product Description
Web Service Patterns: Java Edition describes architectural patterns that can guide you through design patterns (service implementation and usage) and illustrates the different ways in which you can use web services.
Author Paul Monday had two primary goals in writing this book: to show some interesting design patterns that are applicable to web services as well as the broader computing community and to give some hands-on experience using a web service environment.
Monday achieves the first goal by presenting many original, and a few already available, design patterns. The patterns he chooses to discuss illustration the entire web service environment&emdash;from the patterns that make up web service implementation platforms to the patterns for building your own web services. Each pattern covered has a web service implementation section that builds a common application throughout the book.
To fulfill the second goal of providing hands-on experience with web services, Monday chose a single web service environment, Apache Axis, and implemented each pattern using this environment.
By the end of this book, you’ll have deployed more than 15 working web service implementations that show the strengths and weaknesses of web services.
Buy from Amazon Web Services Patterns: Java Edition
This book is a good description of how to bridge traditional OO designs into a web services world. It takes a Java perspective and describes quite well where the differences are in a distributed component model such as WS. It describes very basic GOF patterns, how they have been adapted to J2SE and J2EE, and how these patterns need to be modified to fit into a WS environment.
If you have a Java/OO perspective and some J2EE background building web apps, this book is a very good way of understanding how you will have to modify some approaches to move to distributed, message-based systems with adapters and coarsely-grained data transfers.
Rating: 4 / 5
Now that we have read all the books on the basics of web services and have a good understanding of how they are supposed to work it is time to get down to actually trying to create some decent designs for our web services applications. That is where this book fits in. The book shows how to apply design patterns to a web service architecture in order to solve common design problems. If you are designing a web service architecture you will want to read this book before drawing another UML diagram.
The book starts out by looking at the design patterns used in web services itself. These are the patterns utilized by software such as Apache Axis. This part of the book was interesting but not overly useful. The next part, making up most of the book, covers design patterns that you are likely to need in developing web applications. This part of the book is excellent. Each pattern is discussed in detail and then demonstrated in a case study that is developed throughout the book. Some of the patterns covered are event monitor, observer (with a good comparison of the advantages and disadvantages of the two), business process, asynchronous business process, physical tiers, faux implementation, and service factory. The book covers twenty different patterns so if these don’t sound applicable to your application there is bound to be another that will be applicable.
The book contains only snippets of code from the case study so you will need to download the code in order to get the full value of the case study. The book does include the parts of code that apply to the pattern under discussion. The reader of this book should be comfortable with web services and design patterns in general and be ready for an in-depth discussion of web services architecture.
Rating: 4 / 5
Some of the fonts chosen remember me of some books I read 15 years ago. There are bad recommendations like promoting a distributed architecture in the “Physical Tiers Pattern”. The chapter describe how you can communicate between two processes with RMI or CORBA.
The only two patterns that were not obvious for me were the “Faux Implementation” and “Partial Population”, but few strategies are presented for implementing them.
In overall, the author seems naïve and not very experimented.
Rating: 2 / 5
If you have done a lot of work with OO design, and are designing SOA based systems, this book is for you. It does a brilliant job of explaining how SOA encourages a component Architecture style, rather than a Object Oriented design methodology. Some consequences of that include, 1) passing simple data structures and expecting simple Collections from Services, such as Arrays. 2) Using composition much more, rather than inheritance. 3) Separating the Business Logic (and process) from the Business Data, so that the business process can be exposed at a higher level of abstraction, and shared across multiple Activities that can fulfill the business logic.
This book is still very relevant, and a great read for Architects, developers and Managers.
Rating: 5 / 5
I enjoyed reading this book because it discusses middle-tier issues well. Many Chapters (ex. “SOA Pattern” and “Service Directory Pattern”) are good descriptions of WS, but are not Patterns.There is not enough technical info to implement a WS. There are issues with WS not discussed in this book. Therefore it is not a good summary of WS nor of their Patterns.
Rating: 3 / 5