bklooste 

Partitioned, ordered messaging over Redis Streams: per-key ordering, at-least-once delivery with an explicit error contract, outbox/exactly-once publish, and durable consumer positions.

Typed event projections and view stores over RedisEvents streams: reflection-free dispatch to IProjection<TEvent> handlers and a Redis-backed IViewStore<TView>, usable against any standard topic with no... More information

Given/When/Then scenario testing for xUnit v3 service tests: JSON matching with token expansion, MockServer stubs, and a ServiceTestFixture for spinning up the service under test.

OpenTelemetry tracing extensions for RedisEvents: distributed tracing for Redis Stream operations.

Event-sourced aggregates over RedisEvents: per-aggregate Redis streams as the source of truth, optimistic concurrency, and reflection-free event dispatch. Typed projections/view stores live in the sibling... More information

Redis Streams (RedisEvents) scenario steps for Scenarify: publish/assert on stream messages, seed Redis state, and a RedisFeature that starts alongside the service under test.

Host-neutral health check for RedisEvents stream consumers (Microsoft.Extensions.Diagnostics.HealthChecks), with no ASP.NET Core dependency, so a headless worker and a web service register the same check.

Minimal-API admin endpoints for RedisEvents (and, by reference, the RedisEvents.HealthChecks stream health check), kept separate so a headless worker can reference the core library without pulling in ASP.NET... More information

MessagePack-typed publish/consume for RedisEvents, with size-gated LZ4 compression, kept separate so the core package carries no MessagePack dependency.

Starts Restate workflows from RedisEvents streams in batches: a filter-and-map IBatchHandler<T> base that submits each kept message to its own workflow key over the Restate ingress, retries per item, and blocks... More information

Partitioned, ordered messaging over Redis Streams: per-key ordering, at-least-once delivery with an explicit error contract, outbox/exactly-once publish, and durable consumer positions.

Incremental read-through snapshot cache: merges records newer than a high-water mark into a stored snapshot.

ASP.NET Core health checks and minimal-API admin endpoints for Orange.Lib.Streams, kept separate so a headless worker can reference the core library without pulling in ASP.NET Core.

Azure Blob storage backing for SnapshotStore.

Redis backing for SnapshotStore: a snapshot store, and a record source, over StackExchange.Redis.

Azure Table Storage record source for SnapshotStore: the common two-level shape, Table as the system of record, Blob (SnapshotStore.Azure) as the cached snapshot.