Vulthil 

Hosting abstractions for Vulthil — notably IRestartableHostedService, a marker a background service implements to declare its execution can be stopped and started again cleanly, so infrastructure (such as test... More information

Testing-oriented extensions for asserting and composing application behaviors.

Messaging composition APIs for configuring consumers, queues, and hosted processing.

Messaging contracts for producers/consumers and request/reply boundaries.

Idempotent-receiver (inbox) consume filter for Vulthil.Messaging. Provides exactly-once message processing on top of at-least-once delivery via a pluggable, persistence-agnostic idempotency store.

Azure Cosmos DB idempotency store for Vulthil.Messaging.Inbox — effectively-once message processing (best-effort deduplication layered over idempotent-by-design writes). Cosmos has no cross-partition... More information

Shared Entity Framework Core primitives for Vulthil.Messaging.Inbox — the InboxMessage marker entity and the ISaveInboxMessages context interface, reused by the relational and Cosmos idempotency stores.

Relational Entity Framework Core idempotency store for Vulthil.Messaging.Inbox — transactional exactly-once message processing where the inbox marker and the consumer's writes commit in one transaction. Works... More information

Transactional bus-publish outbox for Vulthil.Messaging. A publish/send filter captures messages published inside a database transaction into the shared outbox table; the outbox relay sends them to the broker... More information

RabbitMQ implementation for the Vulthil messaging abstractions.

Test utilities for validating messaging flows in integration and component tests.

Small result primitives for explicit success/failure flows without exceptions.

Core domain primitives and base abstractions for shared domain logic.

API-layer helpers for endpoints, controllers, and cross-cutting HTTP concerns.

Application-layer building blocks such as handlers, pipelines, and validation helpers.

Infrastructure helpers for persistence, transactions, outbox, and EF Core integration.

Provider-specific EF Core mapping and optimizations for Cosmos DB.

Provider-specific EF Core mapping and optimizations for MySql.

Provider-specific EF Core mapping and optimizations for Npgsql/PostgreSQL.

Shared relational helpers for provider implementations.