Overview
JobRunr provides background processing capabilities for Java applications. The company focuses on serious, reliable job scheduling and execution in Java environments.
Key people
In the news
- We took a little time out this week. So did one of our payments. ⏱️ We used it to update our guided tour for JobRunr v9, and ended up playing with it a lot more than we planned. Quick reminder of what it is: a live JobRunr Pro dashboard running a fake neobank called JobRunr Finance. Here is what changed: 👉 Don't Charge Twice: one click makes a payment whose transfer times out once. You land on that job's new history Chart. The first attempt fails on the transfer step, and on the retry the steps that already ran
- Does the CRA give you 24 hours to fix an actively exploited vulnerability? Not quite. 🕐 In our Cyber Resilience Act webinar, we asked Axel Desmet and Aida Kaloci, tech lawyers at Cresco, exactly that. The 24 hours are for reporting, and there are three clocks: 24 hours: an early warning that says "we have a problem" 72 hours: a notification that says "this is the problem" 14 days after a fix is available: the final report All of it goes to ENISA's Single Reporting Platform, and for manufacturers it applies since 11 September 2026,
- A few weeks ago, Nicholas got billed twice for the same thing. So in our v9 launch webinar, Ronald rebuilt that bug live. 💸 The setup is a monthly invoice run with four steps: 👉 Calculate the usage 👉 Generate the PDF 👉 Charge the customer 👉 Send the invoice email Then the email step throws an exception. JobRunr retries the job, exactly as it should, and the logs show the payment being confirmed again on every single retry. Retries are great, until a step with a side effect sits before the step that failed. That is what durable
- JobRunr exists because my wife let me build it. Right before COVID I was freelancing on a distributed Java project. Messages just got lost because they ended up on a dead letter queue, and nobody could see it happen. So I thought: why not try to fix this? I worked on it for 8 months, from January until September. And because she was that patient with me, I also built a Pro version. The plan was modest: maybe one day it would pay for a nice restaurant date with her. 😅 Today JobRunr is a real business with five people. That still
- Thanks for having us on Quarkusio Insights, Holly Cummins and Eric Deandrea 🙏 The demo in this episode is our favourite way to explain durable jobs in JobRunr 9. An order job bills the customer ➛ generates the invoice ➛ sending the invoice fails. Retry the whole job and you bill the customer again. With jobContext.runStepOnce, finished steps are skipped on the retry and only the failed one runs again. Our new Job Progress Chart in the dasbhoard shows which steps failed, and which ones were skipped on a retry, so you never have
- Processing heavy tasks in a single pipeline can lead to significant risks. If one segment fails, your state is left hanging, creating a complex recovery challenge. Robust background processing is essential to maintain visibility and consistency. Using specialized tooling allows you to monitor every step of the execution, ensuring that even if a failure occurs, the state remains manageable and transparent. The goal is to build resilient systems that don't just process tasks, but offer insight into the workflow itself. #Quarkus
- Ronald is live now with Josh Long to talk about JobRunr 9! https://lnkd.in/ez5EBeVG
- Hi, Spring fans! In this installment we catch up with the latest-and-greatest from JobRunr 9 with founder and engineer Ronald Dehuysser
Something wrong or missing? Send an update. Fixed within 24 hours.