Skip to content

Redis

Terminal window
dotnet add package Surefire.Redis
builder.Services.AddSurefire(options =>
{
options.UseRedis("localhost:6379");
});

This registers both the job store and the notification provider. Notifications use Redis Pub/Sub for real-time event delivery.

If you already have an IConnectionMultiplexer registered in DI:

builder.Services.AddSurefire(options =>
{
options.UseRedis(connection);
});

Redis is a good fit for:

  • High-throughput workloads where claim latency matters
  • High-throughput workloads where low scheduling latency matters
  • Multi-node deployments that need real-time notifications without database-specific features (like PostgreSQL’s LISTEN/NOTIFY)
  • Teams already running Redis infrastructure

The Redis provider supports all Surefire features.