ZeroAlloc.Templates 0.16.2

ZeroAlloc.Templates

dotnet new Web API templates for the ZeroAlloc.* ecosystem. Source-generated and published as Native AOT. The ZeroAlloc primitives — value objects, Result<T, E>, generated validators — allocate nothing per call, and each template's README publishes the measured cost of every framework step above them.

Catalog

Both templates share nine ZeroAlloc libraries: Mediator, Validation, Authorization, Mapping, ValueObjects, Inject, Results, Serialisation and ORM. za-clean adds three more, for 12 libraries in 22 packages: Rest and Resilience for its outbound shipping-quote client, and Telemetry for the [Instrument] proxy on that client's port. za-vertical-slice has no outbound HTTP call, so it has no Rest or Resilience; it takes its telemetry from the Mediator.Telemetry pipeline behavior instead, for nine libraries in 19 packages. Each template uses the telemetry tool that fits its architecture: a layered app instruments its ports, while slices stay self-contained and the mediator pipeline instruments every request. Both share the same ZA.ORM 2 + SQLite persistence (raw Microsoft.Data.Sqlite provider, no DbContext), same xUnit + BenchmarkDotNet + NBomber test/bench fan-out. Apart from za-clean's outbound shipping-quote call, they differ in arrangement, not in functional scope — pick on team comfort, not capability.

Install

dotnet new install ZeroAlloc.Templates

Use

# Clean Architecture
dotnet new za-clean -o MyApp
cd MyApp && dotnet run --project src/MyApp.Api
# In another shell:
curl http://localhost:5000/healthz
# → {"status":"ok"}

# Vertical Slice
dotnet new za-vertical-slice -o MyApp
cd MyApp && dotnet run --project src/MyApp
# In another shell:
curl http://localhost:5000/healthz
# → Healthy

za-clean ships with:

• Four layered projects (Domain, Application, Infrastructure, Api) with NetArchTest-enforced boundaries
• 49 passing tests (12 unit + 5 architecture + 32 integration)
• A BenchmarkDotNet write-pipeline scenario (~1.3 ms / ~36 KB per request through the full middleware stack on Linux/AMD EPYC Postgres CI; see run 26778623747)
• An NBomber read-RPS scenario for load testing under sustained concurrency
• An AGENTS.md that orients Claude Code, Cursor, GitHub Copilot, Codex, and Aider to the codebase

za-vertical-slice ships with:

• One src project (MyApp) — no horizontal layers; concerns live next to the feature that uses them
• Six slices (PlaceOrder, GetOrder, ListOrders, CancelOrder, CreateCustomer, GetCustomer) with request + validator + handler + endpoint + entity co-located per *.cs file
• 70 passing tests (37 unit + 28 integration + 5 NetArchTest convention cases over 4 rules)
• The same BenchmarkDotNet + NBomber benchmark fan-out adapted to the flat PlaceOrderCommand shape

Full tour and rationale: docs/za-clean.md and docs/za-vertical-slice.md.

What's in the box

Paths are for za-clean; za-vertical-slice keeps the same pieces next to the slice that uses them.

License

MIT — see LICENSE.

Maintaining this repo? See CONTRIBUTING.md.