The genesis of this series is the identification of a gap between how development and how operations view technology and measure their success – realizing it is wholly possible for development and operations to be individually successful, but for the organization to fail. 

So what can we do to better align development and operations so that they can speak the same language and work towards the success of the organization as a whole? This article series attempts to address a portion of this problem by presenting operation teams insight into how specific architecture and development decisions affect the day-to-day operational requirements of an application.

The first two articles reviewed decisions that affect the scalability of an application and in particular the challenges in maintaining application state. This article starts a two-part installment that reviews the operational impact of specific decisions made when building a service-oriented architecture (SOA) application.

Read the full article at about:virtualization.