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.

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

← Back to all products