Skip to main content

Creating conditional flows in TPL Dataflow with LinkTo predicates

While building a data processing pipeline with TPL Dataflow, I needed to route messages to different blocks based on specific conditions. The LinkTo method's predicate parameter is the feature I needed to create branching logic in my dataflow network.

In this post, I explore how to use predicates to build conditional flows that are both efficient and maintainable.

Understanding LinkTo predicates

The LinkTo method in TPL Dataflow connects a source block to a target block, creating a pipeline for data to flow through. The method signature includes an optional predicate parameter:

The predicate is a function that evaluates each message and returns true if the message should be sent to the target block, or false if it should be offered to the next linked block in the chain.

A simple example

Let's start with a straightforward example that demonstrates the basic concept. We'll create a pipeline that routes even numbers to one block and odd numbers to another:



How predicate evaluation works

When a message is ready to leave a source block, TPL Dataflow evaluates the predicates in the order the links were created. The first link whose predicate returns true receives the message. If no predicate matches, the message is dropped unless you've set up a catch-all link.

IMPORTANT: This ordering is critical and gives you fine-grained control over message routing.

Creating a ‘catch-all’ path

To ensure no messages are lost, you should always include a default path for messages that don't match any specific condition. You can do this by adding a final link without a predicate:

Real-world example: Processing orders by priority

Here's a more realistic scenario where we process orders based on their priority and value:

Handling unlinked messages

By default, if a message doesn't match any predicate, it's declined and remains in the source block. To handle this gracefully, you have a few options:

So you should always add an alternative path (such as DataflowBlock.NullTarget()) when using a predicate with LinkTo in TPL Dataflow.

Why? When you use a predicate in LinkTo, only items matching the predicate are sent to the target block. Items that do not match are left unprocessed unless you provide another link for them. If you do not handle these items, the source block will never complete, because it waits for all items to be consumed.

More information

Dataflow (Task Parallel Library) - .NET | Microsoft Learn

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...