TutorialIntroduction

Tutorial: Build a Distribution

Build a Distribution: one extractor publishes placed and cancelled orders on one topic, and two loaders deliver them to separate destinations.

You scaffold the first pass and run it. Then you add routing at two levels:

Within a Component. The extractor stamps each order with a CloudEvent type, order-placed or order-cancelled. One loader handles both, each through its own pipeline. The framework picks the pipeline from the type.
Between Components. The System declares which messages each loader receives. The Dapr sidecar applies those rules before a message reaches the loader.

This tutorial is written for intropy CLI 2.1.1 and intropy-templates 2.0.0. A workspace scaffolded with CLI 1.x needs CLI 1.0.1 and --template-version v1.0.3; see Workspaces created before CLI 2.0.

Run these checks before chapter 1:

intropy --version
dotnet --list-sdks
docker info >/dev/null
dapr --version
task --version

Continue when:

intropy prints version 2.1.1 or later.
dotnet --list-sdks includes a 10.x SDK.
Docker exits without error.
Dapr shows CLI and Runtime versions, which confirms dapr init has run.
Task prints a version.
You have a scratch directory you can delete later.

If dapr prints command not found, the Dapr CLI is not installed. It is a separate install from the intropy CLI — see Install the CLI.

What you’ll build

FIG D1Distribution flow: one extractor publishes two message types on the orders topic; the sidecar routes both to the WMS loader, which runs one pipeline per type, and only order-placed to the web loader.

Your code External touchpoint Infrastructure, not your code

The chapters

Each chapter ends in a runnable state.

Scaffold the components — create the extractor and first loader
Create the System and run it — assemble the host and run two orders
Route within a Component — publish cancellations as a second type and give the WMS loader a pipeline for them
Route between Components — add a web loader that receives only placed orders