Articles

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

Subscribe via RSS

Articles

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.
Your access token was stolen. Now what: three layers of defence in your own OpenID provider A bearer token works for whoever holds it. Three layers in redb.Identity: BFF, key-bound tokens via DPoP, fast revocation. Plus what a stolen database yields.
WS-Trust over OAuth: a third transport for the OpenID server, for the estate that runs on SOAP redb.Identity gained a WS-Trust facade: Issue, Validate, Cancel, Renew on the same core routes. The same JWT, the same client registry, WSDL for the generator.
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.
Our OpenID server got a second transport: gRPC beside HTTP, on the same routes redb.Identity now has a gRPC facade: same core routes, same client registry, one token honoured by both transports. What is inside, how to switch it on.
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.
redb 3.7.1: props search up to 100x faster. An alternative to EF Core, or a companion to it Query cost did not depend on what you searched for: the filter sat above GROUP BY. Now the cut happens before the aggregate, on three engines, with no application code changed. Up to 100x on a date range and 5.3x on a full result set in SQL Server.
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.
Running our OpenID server through the official conformance suite, and what it found in us Running the OIDF conformance suite on redb.Identity: setup, running it by hand, and the real bugs it found, including a phone number in the id_token.
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.
Don't stand up a second database just for objects: redb vs MongoDB and RavenDB An object store with types, trees, and real SQL right inside your PostgreSQL/MS SQL/SQLite. FK to objects, EF and Dapper alongside. redb vs Mongo and Raven.
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 real local database in Blazor WebAssembly and MAUI: no DbContext, no Include, no migrations Offline storage for complex graphs and an outbox queue: quick start for MAUI and the browser, everyday operations, and why EF Core just gets in the way here.
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.
redb.Identity, the full tour: a transport-agnostic OAuth 2.1 / OpenID Connect server for .NET — protocol ≠ transport, and no migrations A full OAuth 2.1 / OIDC server for .NET where the protocol is decoupled from the transport: reach token over HTTP, over a bus, or with no network at all.
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.
redb on SQLite, the engineering teardown: a query engine in a C extension, dates stored as numbers, and three bugs we caught so you won't A query engine inside a C extension, dates stored as numbers, and three bugs caught before they reached anyone else.
RedBase 3.2.0 — the SQLite provider you asked for: one file, offline, Blazor WASM and mobile A typed store in a single file: offline, Blazor WASM and mobile, with the same LINQ as the server providers.
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.
REDB inside, part 1.1 — why the same 13 tables stay fast no matter how many classes you throw at them (indexes, the prod log, and a tiny lesson in deleting indexes) Why the same 13 tables stay fast no matter how many classes you throw at them: indexes, a production log, and one lesson in deleting them.
REDB inside, part 1 — the 13 tables the whole engine runs on (with the actual SQL, and why it's not EAV) The 13 tables the whole engine runs on, with the actual SQL and the reason this is not the schema you are expecting.
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.
Why our Free was so far behind Pro — and what we just shipped in RedBase 3.0.0 (with the actual SQL) Why Free lagged so far behind Pro, and what closing that gap took at the SQL level.
An EF Core alternative for .NET apps with complex object graphs — full LINQ, no migrations, no DbContext Full LINQ over complex object graphs with no migrations and no DbContext — what that changes in day-to-day work.