David Linthicum may very well have coined the term “SOA Rage” in his recent posting. His posting had to do with resistance to change that can easily occur with SOA efforts. David says that, “I guess there is a certain amount of rage that’s going to be a part of any change; it’s your job to minimize it.” My issue is that David and others posting on the same topic do not provide any substantive suggestions on how to identify and minimize potential change issues. There are ways to do that. Take a look at Chapters 8 and 9 in Web Services and Service-Oriented Architectures: The Savvy Manager’s Guide. You will find a discussion on how force-field diagrams could help you identify and minimize resistance to change. By the way, I wrote those chapters in 2002. To my knowledge, no other SOA-related book discusses change to the degree I do in that book.

Search this site
Custom Search
Resource Books at Amazon.com
by Martin Kalin
Average Customer Review: 4.5 stars - 16 reviews
Customer Review: I did learn a lot which is all that you can ask for. The book is thin - less than 300 pages, and the author writes in a good conversational style. It is a good tutorial but it probably does not make a good reference as it does not go into too...
by Leonard Richardson, Sam Ruby, David Heinemeier Hansson
Average Customer Review: 4 stars - 46 reviews
Customer Review: Good to hear someone make a convincing argument for a web-based services protocol versus the complexity of SOAP.
by Eben Hewitt
Average Customer Review: 4.5 stars - 12 reviews
Customer Review: Excelente trabajo el de Hewitt. El primer capitulo puede ser suficiente para pagar el precio. Cualquier empresa/arquitecto con una iniciativa SOA debe leer este libro. Completamente recomendado.