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