A Java lambda is all you need for distributed background jobs!
summary
JobRunr converts Java lambdas into persistent, distributed background jobs that run on any JVM and scale on Kubernetes, using SQL or NoSQL for storage and an embeddable in‑process server to process work. It includes an integrated dashboard, automatic retries with configurable backoff, and framework adapters for Spring, Micronaut and Quarkus; it runs on GraalVM and reports around half a billion jobs per day in production, with a commercial Pro edition adding advanced dashboard, batching and chaining features.
AI-written summary · about
chapters (20)
- 0:00Introduction and thanks
- 2:00What is Job Runner
- 3:44Why Job Runner was created
- 9:33Project development story
- 11:48Live coding demo setup
- 12:55Adding Job Runner dependencies
- 13:57Configuring Job Runner
- 15:00Creating a background job
- 16:31Viewing the dashboard
- 17:14Scheduling future jobs
- 18:55Job naming and retries
- 21:11Recurring job scheduling
- 23:01Usage statistics and scale
- 25:14Job Runner internals
- 26:57Real-world use cases
- 27:59Job Runner Pro and sustainability
- 28:23Future features
- 30:19Deployment and Kubernetes
- 31:02Comparison with Quartz
- 31:48Q&A and closing
related talks
32mJobRunr - distributed background processing using only Java 8 lambda's
53mJobRunr - Easy Distributed Job Scheduling
46mAsynchronous Job Processing in Java with JobRunr
48mJava in the Clouds: Pointless and Expensive or Productive and Must-Have?
56mJava on AWS - all the details that matter
39mYour Java AI Agent at Home
49mJava Patterns and Practices for Serverless Applications
06mManaging a Java Batch job with JobStreamer