Workflow Core

Workflow Core is a light weight embeddable workflow engine targeting .NET Standard. Think: long running processes with multiple tasks that need to track state. It supports pluggable persistence and concurrency providers to allow for multi-node clusters.

Announcements

New related project: Conductor

Conductor is a stand-alone workflow server as opposed to a library that uses Workflow Core internally. It exposes an API that allows you to store workflow definitions, track running workflows, manage events and define custom steps and scripts for usage in your workflows.

https://github.com/danielgerlag/conductor

Documentation

See Tutorial here.

Fluent API

Define your workflows with the fluent API.

c# public class MyWorkflow : IWorkflow { public void Build(IWorkflowBuilder<MyData> builder) { builder .StartWith<Task1>() .Then<Task2>() .Then<Task3>(); } }

JSON / YAML Workflow Definitions

Define your workflows in JSON or YAML, need to install WorkFlowCore.DSL

json { "Id": "HelloWorld", "Version": 1, "Steps": [ { "Id": "Hello", "StepType": "MyApp.HelloWorld, MyApp", "NextStepId": "Bye" }, { "Id": "Bye", "StepType": "MyApp.GoodbyeWorld, MyApp" } ] }

yaml Id: HelloWorld Version: 1 Steps: - Id: Hello StepType: MyApp.HelloWorld, MyApp NextStepId: Bye - Id: Bye StepType: MyApp.GoodbyeWorld, MyApp

Sample use cases

• New user workflow ```c# public class MyData { public string Email { get; set; } public string Password { get; set; } public string UserId { get; set; } }

public class MyWorkflow : IWorkflow { public void Build(IWorkflowBuilder builder) {
builder .StartWith() .Input(step => step.Email, data => data.Email) .Input(step => step.Password, data => data.Password) .Output(data => data.UserId, step => step.UserId) .Then() .WaitFor("confirmation", data => data.UserId) .Then() .Input(step => step.UserId, data => data.UserId); } } ```

• Saga Transactions

c# public class MyWorkflow : IWorkflow { public void Build(IWorkflowBuilder<MyData> builder) { builder .StartWith<CreateCustomer>() .Then<PushToSalesforce>() .OnError(WorkflowErrorHandling.Retry, TimeSpan.FromMinutes(10)) .Then<PushToERP>() .OnError(WorkflowErrorHandling.Retry, TimeSpan.FromMinutes(10)); } }

c# builder .StartWith<LogStart>() .Saga(saga => saga .StartWith<Task1>() .CompensateWith<UndoTask1>() .Then<Task2>() .CompensateWith<UndoTask2>() .Then<Task3>() .CompensateWith<UndoTask3>() ) .OnError(Models.WorkflowErrorHandling.Retry, TimeSpan.FromMinutes(10)) .Then<LogEnd>();

Persistence

Since workflows are typically long running processes, they will need to be persisted to storage between steps. There are several persistence providers available as separate Nuget packages.

• MemoryPersistenceProvider (Default provider, for demo and testing purposes)
• MongoDB
• Cosmos DB
• Amazon DynamoDB
• SQL Server
• PostgreSQL
• Sqlite
• MySQL
• Redis

Search

A search index provider can be plugged in to Workflow Core, enabling you to index your workflows and search against the data and state of them. These are also available as separate Nuget packages. * Elasticsearch

Extensions

• User (human) workflows

Samples

• Hello World

• Multiple outcomes

• Passing Data

• Parallel ForEach

• Sync ForEach

• While Loop

• If Statement

• Events

• Activity Workers

• Parallel Tasks

• Saga Transactions (with compensation)

• Scheduled Background Tasks

• Recurring Background Tasks

• Dependency Injection

• Deferred execution & re-entrant steps

• Looping

• Exposing a REST API

• Human(User) Workflow

• Testing

Contributors

• Daniel Gerlag - Initial work
• Jackie Ja
• Aaron Scribner
• Roberto Paterlini

Related Projects

• Conductor (Stand-alone workflow server built on Workflow Core)

Ports

• JWorkflow (Java)
• workflow-es (Node.js)
• liteflow (Python)

License

This project is licensed under the MIT License - see the LICENSE.md file for details