👁 Image
ZeroAlloc.Scheduling 1.2.0

ZeroAlloc.Scheduling

👁 NuGet
👁 Build
👁 AOT
👁 GitHub Sponsors

ZeroAlloc.Scheduling is a source-generated background job scheduler for .NET 8 and .NET 10. Decorate any class with [Job] and the source generator wires up the executor, DI registration, and recurring startup automatically — no reflection, no convention scanning at runtime.

Install

The source generator is bundled into the main package — a single PackageReference is all you need:

dotnet add package ZeroAlloc.Scheduling
dotnet add package ZeroAlloc.Scheduling.InMemory # or EfCore / Redis

The standalone ZeroAlloc.Scheduling.Generator package is still published for backwards compatibility with existing direct PackageReferences, but new consumers should reference only ZeroAlloc.Scheduling.

Example

// 1. Define a job — the generator picks it up automatically
[Job(Every = Every.Hour)]
public sealed class CleanupExpiredSessionsJob : IJob
{
 private readonly ISessionRepository _repo;
 public CleanupExpiredSessionsJob(ISessionRepository repo) => _repo = repo;

 public async ValueTask ExecuteAsync(JobContext ctx, CancellationToken ct)
 => await _repo.DeleteExpiredAsync(ct);
}

// 2. Register — generated AddCleanupExpiredSessionsJob() wires executor + recurring startup
services.AddScheduling()
 .WithInMemoryStore()
 .AddCleanupExpiredSessionsJob();

// 3. Enqueue a one-off job from application code
public class OrderService(IScheduler scheduler)
{
 public async Task CompleteOrderAsync(Order order, CancellationToken ct)
 {
 await ProcessAsync(order, ct);
 await scheduler.EnqueueAsync(new SendOrderConfirmationJob(order.Id), ct);
 }
}

Performance

Head-to-head vs Coravel 5.0.4 (de-facto in-process scheduler) and a hand-rolled BackgroundService + Timer baseline. .NET 10.0.7, i9-12900HK, BenchmarkDotNet v0.15.4.

Honest reading: Coravel's Schedule() is a runtime call that allocates a queue entry; ZA.Scheduling's [Job] registration happens at compile time via source generation — no equivalent runtime cost. For dispatch overhead, ZA matches a hand-written Timer (both inlined to near-zero). The value of the abstraction is [Job] itself (declarative retries / cron / store-backed persistence), not raw dispatch speed.

Full methodology + design analysis: docs/performance.md.

Features

• Source generator — [Job] on a class emits a typed executor, DI extension method, and optional recurring startup (IHostedService)
• Recurring jobs — [Job(Cron = "0 * * * *")] or [Job(Every = Every.Hour)] — scheduled via Cronos at startup
• Retry with backoff — exponential retry up to MaxAttempts (per-job or global); dead-letters after exhaustion
• Multiple backends — InMemory (dev/test), EF Core (SQL Server / PostgreSQL / SQLite), Redis
• Dashboard — embedded HTML/JS dashboard via app.MapJobsDashboard("/jobs")
• Blazor component — <JobsDashboard> Razor component for integration into Blazor apps
• Mediator bridge — [Job] + IRequest<Unit> auto-registers MediatorJobTypeExecutor<T>, routing execution through ZeroAlloc.Mediator pipeline behaviors
• Native AOT compatible — no reflection at runtime; all dispatch resolved at compile time

Dashboard

An embedded HTML/JS dashboard — summary cards for each job state, a live-refreshing table with per-row requeue / delete actions, and fully responsive down to mobile widths.

app.MapJobsDashboard("/jobs");

// Optional: protect with auth
app.MapJobsDashboard("/jobs").RequireAuthorization("AdminPolicy");

👁 Scheduler dashboard — desktop

Tablet (768 × 1024) and mobile (375 × 812) captures live in docs/screenshots/.

See Dashboard for the full endpoint reference and the Blazor component.

Packages

Documentation

License

MIT