devLink 2010 presentation on Workflow and Workflow Systems, using Ruby, MassTransit and WF 4.0 as examples.
1. Myths, Truths and Wishful Thinking Workflow Systems Brandon Satrom devLink2010 http://speakerrate.com/talks/4108
2. About Me Technology Evangelist @ Microsoft Software and Enterprise Architect Based in Austin, TX Husband and Father
3. Why are you here? What is "workflow"? What makes a Workflow System different? What kind of problem is workflow designed to solve? Can workflow problems only be solved by tools? Are workflows always visual? How do I design a workflow system?
4. You Want The Truth?
5. What comes to mind when you hear workflow? Word Association
8. Process Automation
10. Can be maintained by someone other than the original developer
11. Six-Figure Cost
13. Heres the truth
14. Our perception of workflow is wrong
15. Maybe Workflow can be simple
16. State Machine Demo
17. A workflow is a depiction of a sequence of operations, declared as work of a person, a group of persons, an organization of staff, or one or more simple or complex mechanisms. Workflow may be seen as any abstraction of real work, segregated in workshare, work split or other types of ordering. For control purposes, workflow may be a view on real work under a chosen aspect, thus serving as a virtual representation of actual work. The flow being described often refers to a document that is being transferred from one step to another. from http://en.wikipedia.org/wiki/Workflow Workflow: The Cure for Insomnia Definition
18. Workflow: simplistic definitions abstraction of real work coordination of work in a system
19. Isnt that CODE?
20. The Difference is
21. HUMANS are the process
22. TIME Passes...
23. And The only constant is CHANGE.
24. Qualities of Workflow systems
26. External Stimulus Persistence Store Persistent
27. Dynamic Business Change Activity F Divert to new activity
28. Activity D Activity E Rules Store Configurable
31. Not just for workflow State machine Saga Service Buses Workflow
32. Saga Demo (MassTransit)
34. The dangers of seeing too much
35. Workflow Demo (WF 4.0)
36. When Adopting Workflow, Consider Complexity of the problem Skill level of development staff Who keeps it running? Value of a visual representation
37. Any GOOD system will encourage good design Declaratively define the FLOW Define discrete, separate ACTIVITIES Keep the RULES out of code
38. What is "workflow"? What makes a Workflow System different? What kind of problem is workflow designed to solve? Can workflow problems only be solved by tools? Are workflows always visual? How do I design a workflow system? Did We Answer These?