InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Interview: Scott Allan on Windows Workflow Foundation

Posted by Floyd Marinescu on Apr 23, 2007

Sections
Architecture & Design,
Development,
Enterprise Architecture
Topics
.NET ,
Workflow / BPM
Tags
Windows Workflow Foundation
OdeToCode.com's Scott Allan is interviewed by David Totzke on Windows Workflow Foundation, recorded a year ago at VSLive Toronto. Scott talks about the capabilities of Windows Workflow foundation, how it integrates into application development, how Microsoft is using WWF in its own products, DSLs and WWF, and architectural pattterns possible with WWF.

Watch Scott's interview on Windows Workflow Foundation (23:32)

On the topic of emerging architectural patterns for using Windows Workflow, Scott predicts:
I think Windows Workflow is going to be the execution engine. There's certainly the ability to write a lot of code inside of a Workflow, to actually put implementation code inside of a Workflow. I don't think that is going to be the most flexible approach, it's not going to be the best architecture. Workflow has the ability to communicate back to the host process and receive events from the host process during the lifetime of a Workflow through well defined interfaces. You literally define an interface that has public methods and the public events and you tell the Workflow "this is what you're going to be working with". Let's say I'm building a Workflow to download the log files from a web server. I can certainly create activities that do the ftp transfer, the parsing of the log files that do the insertion into the database. But ultimately I think you want to keep those jobs into separate components. The Workflow is really just the shell that says "here's the process we follow, here are the rules". It calls back to the host process which does a lot of the work.
Have any InfoQ readers had a chance to use Windows Workflow yet, if so, what were your experiences?
presentation is dated but still relevant by Floyd Marinescu Posted
it's useful by Huang Caff Posted
  1. Back to top

    presentation is dated but still relevant

    by Floyd Marinescu

    This is the last of a set of interviews recorded before InfoQ launched less than 12 months ago. We decided to still publish it as most of the advice and scenarios decsribed by Scott are fairly timeless and the interview is still a great introduction to WPF for those who don't know that much about it.

  2. Back to top

    it's useful

    by Huang Caff

    there are lots of cases where you're going to want Windows Workflow just to be the driver, the logic
    The tip is very useful for the soltion I'm trying to found in WWF. Thanks!

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.