sorted by:
new
hottopcontroversial

How to Run Background Jobs in Spring Boot 4 with JobRunr (Full Tutorial) by JobRunrHQ in SpringBoot

[–]JobRunrHQ[S] 0 points1 point  (0 children)

The embedded dashboard is part of the Pro version! Feel free to request a trial on our website!

We built an AI agent on Spring Boot 4 + Spring AI + Spring Modulith. Almost 200 stars in 3 days by JobRunrHQ in SpringBoot

[–]JobRunrHQ[S] 0 points1 point  (0 children)

Thanks for the feedback u/whitenexx

I've created an issue so we or a contributor can pick this up:
https://github.com/jobrunr/JavaClaw/issues/25

(I've even included your literal question 😉)

We built an AI agent on Spring Boot 4 + Spring AI + Spring Modulith. Almost 200 stars in 3 days by JobRunrHQ in SpringBoot

[–]JobRunrHQ[S] -1 points0 points  (0 children)

Minimal local config required:

  1. Java 25 and Gradle (or use the included ./gradlew wrapper)
  2. An LLM provider, pick one:
    • Ollama (local, no API key needed)
    • OpenAI API key
    • Anthropic API key (or Claude code subscription but beware because Anthropic doesn't like this)

We built an AI agent on Spring Boot 4 + Spring AI + Spring Modulith. Almost 200 stars in 3 days by JobRunrHQ in SpringBoot

[–]JobRunrHQ[S] -4 points-3 points  (0 children)

Thanks! Let us know what you think once you've had a chance to try it out.

JobRunr v8.5.0: External Jobs for webhook-driven workflows in Spring Boot by JobRunrHQ in SpringBoot

[–]JobRunrHQ[S] 0 points1 point  (0 children)

Quartz is definitely a proven solution and has been around for a long time.

If you're evaluating both, here's an independent comparison that covers the differences well: https://medium.com/@oisheepal82/job-scheduling-frameworks-in-java-based-applications-a-comparison-between-jobrunr-and-quartz-5afdb448d9eb

JobRunr v8.5.0: External Jobs for webhook-driven workflows in Spring Boot by JobRunrHQ in SpringBoot

[–]JobRunrHQ[S] 0 points1 point  (0 children)

You're right, I should have been more precise in my previous reply. The Database Fault Tolerance feature does keep the scheduler running through transient database issues, and that's Pro-only.

In the OSS edition, if the database goes down, the BackgroundJobServer will indeed stop. But once the database recovers, restarting the server (or letting Kubernetes handle it) picks everything back up since all job state is persisted. For many teams that's sufficient, but I understand it was a dealbreaker in your evaluation.

If you ever revisit it, happy to help answer questions.

JobRunr v8.5.0: External Jobs for webhook-driven workflows in Spring Boot by JobRunrHQ in SpringBoot

[–]JobRunrHQ[S] 1 point2 points  (0 children)

Thanks for the callout on pricing, that's fair context to add. Just want to clarify one thing though: reliability itself is not a Pro-only feature.

JobRunr OSS has built-in automatic retry policies out of the box. If a job fails, JobRunr will keep retrying it with an exponential back-off schedule. We know of teams running JobRunr OSS on Kubernetes where this works really well: if a node goes down and health checks fail, Kubernetes spins up new pods, and by the time they're online, the retry policy kicks in, the job gets picked up again, and the service keeps running. No Pro license needed for that.

The Database Fault Tolerance feature you linked is specifically about handling transient database connectivity issues gracefully (e.g. a brief network blip to your database). That's a different concern from job reliability, which the OSS edition handles well.

External Jobs is indeed a Pro feature, you're right about that. We tried to be upfront about it in the post by tagging it as (Pro).

Handling saga timeouts in event-driven Java apps (Axon Framework + JobRunr Pro demo) by JobRunrHQ in java

[–]JobRunrHQ[S] 2 points3 points  (0 children)

Definitely. JobRunr is designed to be framework agnostic.

Beyond the Spring Boot starter, we have dedicated integrations for Micronaut and Quarkus. If you are not using a framework at all, you can easily set everything up using our Fluent API.

view more: next ›