Comments on: Architecting Web Services

By: Ronald S. Miller

Ronald S. Miller — Tue, 09 Mar 2010 21:37:42 +0000

This is not a book for technically oriented people looking for answers on web services. Questions you have on things such as scalability, security, and business models are either not covered or are glossed over at a 50k foot level. Little or no examples are given that will stand up to a developers scrutiny. There are no new ideas here. None. There are no solutions to the important questions here. None. This is yet another book in the “Expert’s Series”. I’ve bought a number of books recently by Apress. For most of these, I have wondered if the author learned the subject in order to write the book. I am convinced that this is the case here.
Rating: 1 / 5

By: Andreas Bjärlestam

Andreas Bjärlestam — Tue, 09 Mar 2010 21:10:04 +0000

This book was so booring that I gave up after reading half of it. It gave me almost no useful information at all. I have not had any practical use of this book so far.
Rating: 2 / 5

By: Ronald S. Miller

Ronald S. Miller — Tue, 09 Mar 2010 19:30:40 +0000

By: Melinda Harper

Melinda Harper — Tue, 09 Mar 2010 19:05:14 +0000

This book is horrible. Save your money and buy a good book. Check out either Developing Java Web Services or Java Web Services Architecture.
Rating: 1 / 5

By: the doctor of geekdom

the doctor of geekdom — Tue, 09 Mar 2010 16:15:00 +0000

This book is probably one of the worst technical books I have ever bought. I wonder if the editors actually read the text. The book starts off with an introduction to Web services which describes them using all sorts of confusing terminology. It uses phrases like sharing content, sharing processes, sharing information and then goes into presentation layers followed by business layers, and wastes 10 pages talking about what a shared process is. I eventually worked out that in fact all the author was trying to say is that a Web service acts like a Remote Procedure call with a request and response. This is simple and only should have required a few lines to explain. And in any case shared processes are nothing to do with Web services. Even worse the author then compares Web services to CORBA and says they both allow code re-use. Does the author know what CORBA is I wonder…The point he should have made is that Web services are stateless and CORBA is a pure inter-object protocol with object activation and sessions. They are not really comparable. The book gets much worse than this and delves into all sorts of meaningless diagrams about architecture. If you want to find out about Web services go to some of the good sites on the web, but don’t waste your money and more importanly time on this book.
Rating: 1 / 5