NexJob 1.0.0

<div align="center">

<br/>

███╗   ██╗███████╗██╗  ██╗     ██╗ ██████╗ ██████╗
████╗  ██║██╔════╝╚██╗██╔╝     ██║██╔═══██╗██╔══██╗
██╔██╗ ██║█████╗   ╚███╔╝      ██║██║   ██║██████╔╝
██║╚██╗██║██╔══╝   ██╔██╗ ██   ██║██║   ██║██╔══██╗
██║ ╚████║███████╗██╔╝ ██╗╚█████╔╝╚██████╔╝██████╔╝
╚═╝  ╚═══╝╚══════╝╚═╝  ╚═╝ ╚════╝  ╚═════╝ ╚═════╝

Background jobs for .NET. Predictable. Observable. No magic.

<br/>

</div>

What is NexJob?

NexJob is a reliable background job processing library for .NET 8. It gives you predictable execution, built-in retries, deadline enforcement, and operational visibility — without the complexity of traditional schedulers.

If you need jobs that must run, fail safely, and leave a trace, NexJob handles it as a first-class concern.

Why not Hangfire?

NexJob was built for developers who want Hangfire-like reliability without the paid storage providers or the hidden complexity.

NexJob is not a drop-in replacement for Hangfire. If you need calendar-based scheduling, distributed execution across untrusted networks, or enterprise plugin ecosystems, Hangfire is the better choice.

Quick Start

dotnet add package NexJob

// 1. Register NexJob and scan for jobs
builder.Services.AddNexJob();
builder.Services.AddNexJobJobs(typeof(Program).Assembly);

// 2. Define a job
public sealed class SendInvoiceJob : IJob<SendInvoiceInput>
{
    private readonly IEmailService _email;

    public SendInvoiceJob(IEmailService email) => _email = email;

    public async Task ExecuteAsync(SendInvoiceInput input, CancellationToken ct)
        => await _email.SendAsync(input.Email, "Your invoice", ct);
}

public sealed record SendInvoiceInput(string Email);

// 3. Enqueue from anywhere
var scheduler = app.Services.GetRequiredService<IScheduler>();
await scheduler.EnqueueAsync<SendInvoiceJob, SendInvoiceInput>(
    new SendInvoiceInput("customer@example.com"),
    deadlineAfter: TimeSpan.FromMinutes(5));

The job expires if not started within 5 minutes — no silent failures, no zombie jobs.

Core Features

• IJob / IJob<T> — simple and structured job interfaces
• Predictable retries — exponential backoff with configurable policies, global + per-job [Retry]
• Deadline enforcement — jobs expire if not executed in time (deadlineAfter)
• Dead-letter handlers — automatic fallback when all retries are exhausted
• Concurrency throttling — [Throttle] attribute for per-resource limits
• Job continuations — chain jobs with parent/child relationships
• Idempotency — DuplicatePolicy controls re-enqueue behavior
• Recurring jobs — via code or appsettings.json
• Job filters — IJobExecutionFilter middleware for cross-cutting behaviour
• Job retention — automatic cleanup of terminal jobs with configurable TTL
• OpenTelemetry — traces and metrics built-in
• Built-in dashboard — standalone dark UI, zero configuration

Storage Providers

All providers implement IRuntimeSettingsStore — runtime configuration persists across restarts.

Dashboard

The dashboard provides a visual timeline of every job's lifecycle — no log reconstruction needed. See failures, retries, expired jobs, and execution timing at a glance.

app.UseNexJobDashboard("/dashboard");

One line. No configuration required.

Documentation

Complete documentation is in the wiki. Key pages:

• Mental Model — how NexJob works, read this first
• Getting Started — run your first job in 2 minutes
• Best Practices — production guidelines
• Troubleshooting — debug common issues
• Common Scenarios — real-world use cases with code

Benchmarks

Measured per individual enqueue operation:

NexJob is 2.87× faster and uses 85% less memory per enqueue. Benchmarks run with BenchmarkDotNet against comparable configurations.

Roadmap

v0.4.0  ✅ Deadlines, dead-letter handlers, wake-up signaling
v0.5.0  ✅ Wake-up channel, recurring jobs, dashboard timeline
v0.6.0  ✅ Distributed reliability tests, recurring config redesign
v0.7.0  ✅ DuplicatePolicy, atomic commits, AI execution system
v0.8.0  ✅ Filters, persistent settings, job retention, wiki
v1.0.0  ○ API freeze, production hardened
v2.0.0  ○ Distributed coordination, multi-node consistency

<div align="center"> <br/>

Built with obsession over developer experience and production reliability.

<br/>

   © 2025 Luciano Azevedo

</div>