Using hangfire within a micro services infrastructure using database schemas?


#1

is there a recommended way of using hangfire In an infrastructure of many API services where more than one separate API may decide to use hangfire?

Currently I will create a separate database for each service boundary so each services jobs would be stored separately in their own DB tables.

Is there a way to specify a database schema for hangfire to build its infrastructure instead of an entire database?


#2

Why not just to specify different storage options for hangifre? For example, specifing Db index in RedisStorageOptions in case of using Redis.


#3

is there an equivalent for DB schema when using postgres or sql storage?


#4

For SQL Server yes, Hangfire.SqlServer.SqlServerStorageOptions, Field SchemaName