Articles on redb.Route

Reference articles on the redb ecosystem — redb.Route: deep dives, mechanisms and working examples.

Subscribe via RSS

Articles on redb.Route

AS4 in .NET without a Java MSH: ebMS 3.0, WS-Security and non-repudiation receipts as a route step AS4 brings signed, encrypted document exchange to EU government and enterprise networks, now as a native redb.Route connector with no Java MSH or gateway.
Redis in .NET routes: cache, Pub/Sub, Streams with consumer groups and Claim Check in one connector The Redis connector for redb.Route: every data structure as a route step, Pub/Sub, Streams with consumer groups, a list as a queue, and Claim Check on Redis.
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.
Expressions in .NET routes: one language for conditions, values and templates, compiled to IL header.amount > 1000 compiles to a delegate; conditions, ${...} and Expr() share one grammar. How it differs from Simple in Apache Camel.
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.
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.
What an integration layer really costs: a TMS backend counted line by line An integration layer on WSO2 MI and EF Core, counted line by line: what a real TMS backend costs to keep running.
Reference architecture for a payment platform on .NET: the ledger, transaction boundaries, modules, and the cluster Reference architecture for a payment platform: the ledger model, transaction boundaries, the module split and cluster topology.
A payment platform on .NET: what it actually costs, and how much of it you never have to write What a payment platform on .NET actually costs to build, and how much of it is already solved by the runtime it runs on.
redb 3.4.0: day-two operations for a .NET stack — replay what failed, hot-patch the framework, lock down the control plane Day-two operations for a .NET stack: replay what failed, hot-patch the framework without a rebuild, and lock down the control plane.
The night job that carves its own partitions: cron, a plpgsql function, and a Splitter A nightly job that carves its own partitions: a cron trigger, a plpgsql function and a Splitter, with no orchestrator in between.
The Amazon SQS + SNS connector in redb.Route: the whole queue in one URI — competing consumers, at-least-once, and pub/sub via SNS→SQS. Still leaving MassTransit The whole queue in one URI: competing consumers, at-least-once delivery, and publish-subscribe through SNS to SQS.
The RabbitMQ connector in redb.Route: the whole broker in one URI — RPC, competing consumers, dead-lettering. Still leaving MassTransit The whole broker in one URI: RPC, competing consumers and dead-lettering, without a separate configuration layer.
redb 3.3.0: an enterprise .NET stack you actually own — typed store, a homegrown Apache Camel, and a runtime with a dashboard (all free) An enterprise .NET stack you actually own: a typed store, a homegrown Apache Camel and a runtime with a dashboard.
Two routes in an evening: from a debug worker to an enterprise runtime with redb.Route + Tsak Two routes in an evening: how a debug worker turns into a runtime with a dashboard, deploys and hot reload.
Leaving MassTransit for a Camel state of mind: the Kafka connector, Scatter-Gather, and what really happens under a transaction The Kafka connector, the Scatter-Gather pattern, and what actually happens to a transaction when branches run in parallel.
A homegrown Apache Camel for .NET, dissected: the HTTP connector with no ASP.NET MVC + the Content-Based Router pattern An HTTP connector built straight on Kestrel with no ASP.NET MVC, and the Content-Based Router pattern on top of it.
From chat demo to enterprise agent platform: `redb.Route.Llm` 3.1.1 — streaming, RAG, governance, jury arbitration, sub-agents, real reports and forecasts What separates a chat demo from an agent platform: streaming, RAG, governance, jury arbitration, sub-agents and reports you can act on.
redb.Route 3.1.0 — LLM as just another connector: `.To("llm://claude")` and tools-as-routes An LLM behind the same URI as any other transport, and existing routes turned into tools the model can call.
Enterprise Integration Patterns in .NET, the deep-dive series — Part 1: the four in-memory channels (and the Exchange they carry) The four in-memory channels every route is built from, and the Exchange that travels through them.