redb.Route

integration framework

The .NET equivalent of Apache Camel

Enterprise integration framework for .NET — wire any system to any system in a few lines of C#. A fluent DSL builds From → Process → To pipelines. No XML, no message-bus lock-in, no per-endpoint license fees.

GitHub ↗ NuGet ↗llms.txt ↗
25
transports
30+
EIP patterns
32
NuGet packages
OTel
built-in

What's inside

  • Brokers & messaging: Kafka, RabbitMQ, Azure Service Bus, IBM MQ, Amazon SQS/SNS, MQTT 5.0, AMQP 1.0, Redis.
  • Network & web: HTTP, gRPC, WebSocket, SignalR, raw TCP, Telegram Bot API.
  • Files & storage: File, FTP/SFTP, AWS S3 / MinIO, redb typed object storage.
  • Data & search: SQL (ADO.NET), Elasticsearch, LDAP / Active Directory, Firebase.
  • AI / LLM: llm: connector (OpenAI-compatible — 14 APIs — + native Anthropic, token streaming), MCP client (mcp:), and .AsLlmTool() to expose any transport as an LLM-callable tool.
  • 30+ EIP patterns (Splitter, Aggregator, CBR, Saga, Circuit Breaker, Idempotent Consumer, Scatter-Gather…), compiled expression engine, transactional routes, OpenTelemetry built-in.
  • Runs in production on redb.Tsak: .tpkg modules, hot-reload, clustering, REST/CLI/dashboard. 32 packages, Apache 2.0.

Latest releases

  • 3.7.1
    • redb.Route.Sftp — SSH.NET 2025.1.0 ([GHSA-q939-rpr3-3284], high), declared directly.
    • The Kafka, RabbitMQ and Redis test projects pulled the same vulnerable SSH.NET 2024.2.0
  • 3.7.0
    • redb.Route.Grpc — a gRPC method address is now a route, and many of them share one port. The
    • redb.Route.Grpc — real gRPC statuses out of a route. The consumer maps the transport-neutral
    • redb.Route.Grpc — typed .proto services without generated server stubs. Envelope=Auto keeps the
    • redb.Route.Grpc — server streaming, mTLS, health. An IAsyncEnumerable reply body is written one
  • 3.6.0
    • Fluent DSL builders — endpoint URIs now round-trip through the parser; space-bearing values no longer
    • redb.Route.Llm — conversation isolation no longer depends on tree-filter semantics
    • redb.Route.Llm — tool routes now run on a child of the agent exchange, not on a naked one.
    • redb.Route.Llm — the run's principal and audit tags reach tools. The engine copied a hard-coded
All releases (20) →

Articles on redb.Route

A directory is an integration: file exchange in .NET without cron, FileSystemWatcher or hand-rolled pollers Polling, waiting for a file to finish being written, idempotency and atomic temp+rename writes, as an ordinary route step.
Control Bus for .NET routes: stop, restart and react to route events at runtime Manage routes at runtime by sending a message: start, stop, suspend, restart, plus a consumer that turns route lifecycle events into messages.
SOAP in .NET without WCF: WS-Security, MTOM and ?wsdl as a route step SOAP with WS-Security, MTOM and WSDL publishing is now a native redb.Route connector: no WCF, no CoreWCF, no standalone gateway.
Architecture of a ticket-search engine: three GDS, rail, and an itinerary changed mid-journey A reference architecture for a ticket-search engine on the redb ecosystem: a canonical model, Scatter-Gather across three GDS and rail, an itinerary tree, and saga reissue on the road.
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.
AS2 in .NET without a separate Java gateway: EDI with trading partners, right inside the route AS2 — signed, encrypted S/MIME document exchange with trading partners — is now a native redb.Route connector, not an external gateway.
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.Route (22) →

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

← Back to all products