The most practicable way to think about services and orchestration is as independent layers in which the process layer is the calling application to the services to extract both data and behavior needed to form cohesive orchestrations.
That's just the beginning, David Linthicum asserts in Considering services and orchestration.
"Orchestration is a necessity if you build a SOA, intra- or inter-organization," Linthicum explains.
So, what else to take into account? Plenty, in fact, from Linthicum's perspective there are at least nine such realities.
Posted by Tom Sullivan on March 14, 2008 10:59 AM
![[VoiceIndigo Mobilize - Listen to podcasts on your mobile phone]](http://www.voiceindigo.com/ht/images/mobilize_logo_sm.gif){kind=logo}
