The latest release from Zapthink discusses that age-old axiom of how you shouldn’t run before you can walk and it’s applicability to SOA. According to ZapThink:

“… success with SOA rarely necessitates comprehensive change; instead, architects who choose their SOA battles carefully can deliver on SOA’s promises to the business via projects of limited scope. Architects who miss this point often set the bar for SOA success too high …”

This isn’t particularly new: for example, we had the same problems when CORBA and DCE first came on the scene and everything just had to be distributed and object-based. Some could argue that this in turn lead to a lot of backlash. Therefore, lessons like this should be learned and it’s good to see the article, particularly given the large amount of hype that still surrounds SOA. Hopefully most people are experienced enough to realise this, but it’s often the case that the obvious tends not to be so obvious after all.

Read more at: InfoQ