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