Soa Sucks Customer Reviews and Feedback

From Everything.Sucks

Revision as of 15:42, 17 September 2020 by JGA (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Service-oriented architecture (SOA) is a style of software design where services are provided to the other components by application components, through a communication protocol over a network. A SOA service is a discrete unit of functionality that can be accessed remotely and acted upon and updated independently, such as retrieving a credit card statement online.

Gaurav shares his experience on Amazon, "Service Oriented Architecture with Java: Using SOA and web services to build powerful Java applications, is the first book that is being given just one star. I had the misfortune of ordering and attempting to read this one. These are some of my gripes: . If the aim is to learn about JAX-WS, JAXB, WSDL, SOAP etc in more detail than a reading it off a billboard then this book is not for you. This was akin to reading a ppt or off a billboard. Yes, there was some useful information but it was more like a pointer that I had to follow through with the aid of to get comfortable with it. This book will give you a lot of jargon in 175 pages but that is about it. And it will also make your wallet lighter. I could have used the JAXB tutorial on the JAXB net site and that would have covered JAXB and I assure you that is awesome. JAX-WS details someplace else. Similarly for SOA, Mike Hansen's book would do the trick. Unfortunately, I would have to agree that the absence of writers such as E Rusty Harold, Monson-Haefel is being felt in the SOA and Java Web Service arena. . Overall the quality of writing style is confusing and terminology and acronyms are scattered throughout and in some cases, not explained satisfactorily at all. For instance "3GL", "4GL", "M and A" etc. Repetitions galore in 175 pages - start to finish. It would appear as if the content in the book has not been proof-read and the authors have collaborated albeit still have managed to essentially hash the same stuff again and again. This is a book about SOA but does that imply that some SOA aspects have to be repeated again and again? For instance: "Why SOA" in the first chapter 1 and then the same hashup in the last chapter."


Be the first to tell the world why Soa sucks!

I certify that this review is based on my own experiece and is my opinion of this person or business. I have not been offered any incentive or payment to write this review.


Enter Code