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