David Chappell explains why – Workflow matters
David Chappell is an authoritative commentator on middle-ware, in this post he explains why workflow is important and confirms that the addition of workflow services to Windows will also be important:
Yet one application of workflow technology is by far the most important in a service-oriented world: providing logic that coordinates the activities of a group of services. Sometimes referred to as orchestration rather than workflow, this coordination is fundamental to creating composite applications. And composite applications look like today’s most promising approach to building new software that really meets business needs.
As I’ve argued elsewhere (here and, at greater length, here), the coordinating logic of a composite app requires a particular kind of supporting platform. Workflow/orchestration technologies provide this platform, and without it, composite applications are tough to build. Developers and architects will need to learn how and when to use what workflow offers, something that’s sure to take time. Still, by including workflow in Windows, Microsoft is clearly indicating that it views this technology as a standard part of the modern developer toolkit.