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 Thomas Erl
Average Customer Review: 4.5 stars - 32 reviews
Customer Review: It's a practical guide on defining service characteristics and design principles in multiple levels, from component implementation to application design to enterprise architecture. Very digestive material.
by Poornachandra Sarang, Frank Jennings, Matjaz Juric, Ramesh Loganathan
Average Customer Review: 4 stars - 7 reviews
Customer Review: The authors having had real world experience on how to develop SOA, have presented this book focusing more on practicality. They have worked in different websites and online companies where they specialized either in the development of SOA or ...
by Tony Willis
Average Customer Review: 1 star - 1 review
Customer Review: Since the topic of this book is BPEL you might be surprised to find the question "Have you heard of business process execution language, or BPEL?" more than a third of the way through it, on page 68. But there's an explanation: the book consist...