frodase / minion Goto Github PK

It would be great if the execution time of every job was stored along with the job. This opens up the possibility to have alerts on slow performing jobs.

Hey there, just wanted to know if there was a quick comparison between Minion and Hangfire.

Is it built to replace Hangfire at all?

thanks in advance :)

Add a dashboard to view the status of all jobs, restart jobs and manage errors.

We often deploy logically separate services as a single deployment unit using a single service or web app as the host and then boot up the logically separate services within the same application / app domain.

Due to the static Configuration property of the MinionConfiguration, this can cause issues when the MinionConfiguration is configured by multiple logical services. I've had a cursory look and it appears that the static nature of the MinionConfiguration can be fairly easily removed. This would mean that a MinionConfiguration instance is constructed and passed into BatchEngine for example as a constructor parameter.

var minionConfiguration = new MinionConfiguration();
minionConfiguration.UseSqlStorage("<connection string>");

var engine = new BatchEngine(minionConfiguration);
engine.Start();

Is this something you'd be open to adding?

Just wondering if there are any plans to extend the stores so they can be queried for existing jobs and then manipulate them (deletes particularly).

For recurring jobs, I would like to avoid rescheduling the job every time the app starts up but I cannot query the store (I think) to determine if I should queue a new schedule or not.

Thanks!

Implement heart beat in IBatchStore

To setup and run the server is a bit verbose. You should not have to pass common services around.

It would be great to have a redis implementation.
Start by creating a new project, "Minion.Redis", implement IBatchStore for redis.
Create a new nuspec file, "Froda.Minion.Redis"