Migrate to JobRunr

From Quartz Scheduler Medium

2-4 hours for typical projects

Quartz requires Job classes, triggers, and complex configuration. JobRunr uses simple lambdas or JobRequest/JobRequestHandler.

JobDetail job = JobBuilder.newJob(EmailJob.class)
    .withIdentity("sendEmail")
    .usingJobData("userId", id)
    .build();

Trigger trigger = TriggerBuilder.newTrigger()
    .startNow()
    .build();

scheduler.scheduleJob(job, trigger);

BackgroundJob.enqueue(
    () -> emailService.send(userId)
);

What changes:

• Remove Job interface implementations
• Remove trigger configuration
• Replace with lambda calls or job requests
• Delete 11 Quartz tables, JobRunr manages its own schema

Full Quartz Migration Guide →

From Spring @Scheduled Easy

30 minutes to 1 hour

Spring @Scheduled is simple but doesn't persist jobs or handle multiple instances. JobRunr adds reliability.

@Scheduled(cron = "0 0 9 * * *")
public void dailyReport() {
    reportService.generate();
}

@Recurring(id = "daily-report",
    cron = "0 0 9 * * *")
public void dailyReport() {
    reportService.generate();
}

What you gain:

• Jobs survive application restarts
• No duplicate execution across instances
• Built-in dashboard and monitoring
• Automatic retries on failure

Spring Boot Starter Configuration → | Java Scheduling Guide →

From Spring Batch Medium

Varies by complexity

Spring Batch is for ETL and chunk processing. JobRunr is for background tasks. You might need both, or just JobRunr.

Use JobRunr instead when:

• You're processing items individually, not in chunks
• You don't need reader/processor/writer pattern
• You want simpler code without batch infrastructure

Keep Spring Batch when:

• You're doing true ETL workloads
• You need chunk-based transaction management
• You're processing millions of records in a single job

Spring Batch vs JobRunr →

From Hangfire (.NET) Easy

1-2 hours (API is nearly identical)

Moving from .NET to Java? JobRunr's API was inspired by Hangfire. The concepts map directly.

BackgroundJob.Enqueue(
    () => Console.WriteLine("Hello!")
);

BackgroundJob.Schedule(
    () => SendEmail(userId),
    TimeSpan.FromDays(7)
);

BackgroundJob.enqueue(
    () -> System.out.println("Hello!")
);

BackgroundJob.schedule(
    Instant.now().plus(Duration.ofDays(7)),
    () -> sendEmail(userId)
);

Hangfire for Java Guide →

From Custom/Homegrown Scheduler Varies

Depends on current implementation

Built your own job scheduler? Time to stop maintaining it.

Common patterns to replace:

• Database polling loops → JobRunr handles this
• Custom locking logic → Built into JobRunr
• Retry mechanisms → Automatic with exponential backoff
• Status tracking tables → JobRunr manages its own schema
• Admin UI → Built-in dashboard

Why DIY Schedulers Fail →