Tutorial: Build a transactional integration

Build one transactional integration from empty send steps to a running System.

A Transactional Integration is one Component that moves messages from one source to one destination through its own internal queue. Its receive side sweeps the source, publishes each file to the queue, and deletes the file once it is on the queue; its send pipeline delivers the message from the queue to the destination. Conceptually it is similar to a BizTalk receive port, MessageBox, and send port in one deployable unit.

The framework owns the receive side. You scaffold the Component, implement the send pipeline, run the tests, create the host, and add idempotency and business incidents.

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.

Verify prerequisites

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. It is optional — without it, the chapters use plain shell commands.
• 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

A Transactional Integration that moves orders from a source folder to a destination folder through one Component.

FIG T1System view: source system → order-sync Component → destination system.

Inside the Component, the framework’s receive side feeds the internal queue and your send pipeline drains it:

FIG T2Component view: framework receive side → internal queue → send pipeline.

Your code External touchpoint Infrastructure, not your code

The receive side is framework code. You write the send steps: deserialize, extract, validate, transform, serialize, send.

The chapters

Each chapter ends with a command you can run.

1. Scaffold the component — create the empty Component and inspect the failing tests
2. The model and the Deserializer — define the message and context values
3. Extract, validate, transform — implement the business steps
4. Serialize, send, and run — finish the pipeline and run the host
5. Idempotency and business incidents — wire deduplication and incident routing