Eternet.AspNetCore.Hangfire.PostgreSql 1.0.5

Eternet.AspNetCore.Hangfire.PostgreSql

Common Hangfire PostgreSQL registration for Eternet ASP.NET Core applications.

The package is storage-topology neutral. It configures Hangfire PostgreSQL consistently, but it does not decide whether a service uses an existing dedicated Hangfire database, the application database with a hangfire schema, or a custom connection factory. That decision belongs to each application's data plane.

Existing dedicated database

Use this when the application already has an operational Hangfire database and must preserve jobs, history, permissions, backup/restore boundaries, or pool budgets.

services.AddEternetHangfirePostgreSql(configuration, options =>
{
    options.ConnectionStringName = "HangfirePostgreSql";
    options.RegisterServer = true;
    options.WorkerCount = 2;
    options.Queues = ["default"];
});

Application database and schema

Use this only when the application explicitly owns Hangfire storage in its own database. Schema creation is opt-in so production DDL is not triggered by default.

services.AddEternetHangfirePostgreSql(configuration, options =>
{
    options.ConnectionStringName = "PostgreSql";
    options.SchemaName = "hangfire";
    options.PrepareSchemaIfNecessary = true;
    options.RegisterServer = true;
});

Custom connection handling

Applications can preserve a custom resolver, provide Hangfire's IConnectionFactory, or reuse an existing NpgsqlDataSource. The helper does not add or rewrite MaxPoolSize, MinPoolSize, or other pool parameters.

services.AddEternetHangfirePostgreSql(configuration, options =>
{
    options.ConnectionStringResolver = (serviceProvider, _) =>
        serviceProvider.GetRequiredService<IOptions<DatabaseSettings>>().Value.HangfireConnectionString;
});

services.AddEternetHangfirePostgreSql(configuration, options =>
{
    options.ConnectionFactoryResolver = (serviceProvider, _) =>
        serviceProvider.GetRequiredService<IConnectionFactory>();
});

services.AddEternetHangfirePostgreSql(configuration, options =>
{
    options.DataSourceResolver = (serviceProvider, _) =>
        serviceProvider.GetRequiredService<NpgsqlDataSource>();
});

Workers

RegisterServer defaults to false. Enable it only in hosts that should run Hangfire workers. WorkerCount = 2 and Queues = ["default"] are baseline values; applications should tune them per environment and account for the effective worker count across all running instances.

Control plane

Hangfire storage location is independent from Eternet.Mediator stateful commands and the future control plane. The control plane standardizes contracts, identity, execution, observability, and operation; it must not force the physical database used by Hangfire during the transition.