ResQ Building Blocks

Reusable .NET building blocks for Clean / Hexagonal (Ports & Adapters) architecture — the frame, published to NuGet, so every ResQ .NET service is built the same way. This repo holds the paradigm and primitives, not the domain: base classes, port interfaces, and adapters carry zero business logic. The actual ResQ domain, use-cases, and moat stay private.

Sibling to dotnet-sdk (the proto-generated interop client). This repo is how we build services; dotnet-sdk is what we expose over the wire.

The hexagon → the packages

        Driving adapters                Core                 Driven adapters
   (Web / CLI / Events)  ─►  Application ─► Domain  ◄─  (Persistence / Messaging / External)
                               (ports defined here)      (ports implemented here)

Package	Ring	Status	Contents
ResQ.BuildingBlocks.Domain	Domain (inner)	✅	Entity, AggregateRoot, ValueObject, IDomainEvent, Result/Error, Guard — dependency-free
ResQ.BuildingBlocks.Application	Application	✅	CQRS contracts, driven ports (IUnitOfWork/IClock/IDomainEventDispatcher), pipeline behaviors
ResQ.BuildingBlocks.Adapters.Web	Driving	✅	REPR endpoints, Result→HTTP mapping, ProblemDetails, versioning, OpenAPI
ResQ.BuildingBlocks.Adapters.Persistence	Driven	✅	EF Core repository base, Specification eval, UnitOfWork, Outbox, Idempotency
ResQ.BuildingBlocks.Adapters.Messaging	Driven	✅	broker abstractions, consumer base
ResQ.BuildingBlocks.ServiceDefaults	Cross-cutting	✅	OpenTelemetry, health checks, resilience, config validation
ResQ.BuildingBlocks.Testing	—	✅	fixtures/harness for the paradigm

Plus templates/resq-service (a dotnet new template) and samples/Widgets (a throwaway, non-moat reference service showing the whole hexagon).

Operational notes

Outbox relay is single-instance

⚠️ Run exactly one OutboxRelay instance per outbox table. The relay polls, publishes, and stamps rows but does not claim them first, so two instances against the same table would each publish every pending row (duplicate delivery). Downstream consumers dedupe via the inbox/idempotency store, so duplicates are safe but wasteful. In a multi-replica deployment, gate the hosted service behind leader election, a single-replica deployment, or a scheduled singleton job.

A provider-agnostic optimistic row claim (LockedUntil/ProcessorId or a RowVersion + WHERE-guarded ExecuteUpdate) was evaluated and deliberately deferred: a clean batch claim needs an ExecuteUpdate over an ordered, limited query, which EF Core cannot translate uniformly across providers (SQLite has no UPDATE … LIMIT) without dropping to raw SQL. Until a claim is added, single-instance operation is the supported contract.

A transient broker outage does not strand the backlog: a publish failure keeps the row's attempt budget intact, abandons the current batch, and retries the whole backlog on the next poll. Only message-specific faults (unresolvable event type, undeserializable payload) consume attempts and park a poison row after OutboxOptions.MaxAttempts.

Repo mechanics (inspired by dotnet/extensions)

• Central Package Management — every version pinned once in Directory.Packages.props.
• Directory.Build.props (root: language/analysis/identity) + src/Directory.Build.props (packaging: multi-target net8.0;net9.0, SourceLink, .snupkg symbols, docs).
• Git-tag versioning via MinVer — tag v1.2.3 → package 1.2.3.
• CI (.github/workflows/ci.yml): restore → build → test → pack on every push; dotnet nuget push on a v* tag.

Consume

dotnet add package ResQ.BuildingBlocks.Domain
dotnet add package ResQ.BuildingBlocks.Application

Build locally

dotnet build -c Release
dotnet test  -c Release
dotnet pack  -c Release -o artifacts

Publish

Push a tag: git tag v0.1.0 && git push --tags. CI packs and pushes to NuGet (needs the NUGET_API_KEY secret + a nuget environment).

---

Apache-2.0 · © ResQ Systems, Inc.