redb.Tsak

runtime container

The .NET analogue of Apache Camel K

The runtime container for redb.Route integration pipelines. Drop DLLs into a folder; start, stop and hot-reload them at runtime. Scale across nodes with leader election. Watch every message, error and restart — from a REST API, a 30-command CLI, or a Blazor dashboard. Zero downtime, production-tested. The missing piece between a hand-rolled Worker Service and a heavyweight enterprise ESB.

GitHub ↗ NuGet ↗llms.txt ↗
351
tests passing
32
REST endpoints
30
CLI commands
Blazor
dashboard

What's inside

  • Module-based deployment: drop a .dll or .tpkg into Libs/ — Tsak loads it and hot-swaps updates without dropping in-flight messages; per-module AssemblyLoadContext isolation.
  • Three deployment modes: standalone (in-memory) · single-node + redb (durable RTTI-storage state) · cluster (leader election + automatic context redistribution).
  • Three API modes (full / headless / readonly) + 5-layer deep-merge configuration that hot-reloads — no code changes, no restarts.
  • Cluster: epoch-fenced leader election, node registry with heartbeats, rolling hot-reload; pluggable backends (Kubernetes / etcd / Redis / Consul).
  • Observability: per-process & per-route metrics, ring-buffer logs, OpenTelemetry, optional Prometheus; watchdog auto-restarts hung routes; Quartz scheduler in every context.
  • Operate it: 32-endpoint REST API + typed C# client, 30-command CLI, 10-page Blazor dashboard. Security: API key + HMAC-SHA256, roles, revocation, redb-backed key store.

Latest releases

All releases (27) →

Articles on redb.Tsak

XML routes in redb.Route: a schema the editor picks up, checks at build time, modules swapped live A route in .route.xml runs on the same engine as C#: completion in VS Code, package checks inside dotnet build, a graph editor and hot module swap.
redb for business: your team writes business logic, the infrastructure is already built With redb your team writes only business logic: what the ecosystem replaces, what it costs, which risks it removes, and what to know before you start.
redb 4.0: XML routes, lazy references, unique keys and WS-Trust in one major release One major release across the ecosystem: what's new in redb.Core, Route, Tsak and Identity, what got fixed on security, and what breaks.
Microservices in .NET without building a platform: a cluster of workers, one dashboard, hot-swapped modules The same artifact deploys as a monolith and as a cluster of microservices. Same modules, one dashboard over every worker, hot swap with no container restart.
redb 3.7: our own gRPC wire, cutting props before the aggregate, and a release withdrawn a day later Our own gRPC wire in Route, props cut before the aggregate in redb.Core, Tsak closed by default, a second Identity facade. And 3.7.0, withdrawn a day later.
redb 3.6.0: a bug report that turned out to live in six providers — plus AS2/EDI and a shared port A user's report exposed a cross-conversation leak in the core query provider — 6 of 6. Also in 3.6.0: AS2/EDI, a shared Kestrel, Camel parity.
A TMS backend, architecturally: cluster, coordinate streams and a typed object store How a TMS backend is built: fifteen modules over three nodes, coordinate streams through Kafka and Redis, and a typed object store.
We ported a module off an ESB and the code grew 1.7×. That was the right outcome One module moved off the ESB and the code grew 1.7 times. Why that was the right outcome, counted module by module.
All articles on redb.Tsak (14) →

Docs and examples for this product are coming soon. For now, see GitHub and the README.

← Back to all products