Conference Architect Insight 2007, Service Capsules - A Language and Patterns Perspective on Service Design and Implementation

Arvindra Sehmi, Microsoft EMEA DPE

- This session is about emerging ideias and concepts
- The term Service Capsule is not an official approved or endorsed by Microsoft
- The term Service Capsule is used simply to distinguish from the term Service
- This session is not supported by Microsoft

- Business Processes actors go through different interactions
- We need to know what sequence to use when calling services that perform those actions
- Humans will always be envolved in these workflows
- What kind of business protocols should we use to automate this?
- There is much more to the design of robust systems then good tools
- Business process, knowledge concepts
- A BP consists in coordinating a number of actions or tasks
- A BP generates business knowledge, which is composed of business facts
- Three levels of business automation
 - Coordination
 - Infrastructure
 - Information
- Business roles are supported by information and infrastructure roles
- Services and Workflow, workflow-backed service contracts
- A Windows Workflow sample shows it is possible to model service calls sequence (duh!)
- We can represent the metadata of the workflow as we wish, it could be a BPEL document, SSDL or WS-CL
- A workflow as a service

(Nota: saí antes do fim porque a sessão tornou-se numa introdução ao WF)



Published Monday, March 05, 2007 6:45 PM by António Cruz
Filed under , , , ,

Comments

 

Ant said:

March 5, 2007 7:59 PM
 

canoas'blog said:

March 8, 2007 2:06 AM