|
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. |
|
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. |
|
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. |