Run JobRunr in production without the surprises
One hour, live, on the part of JobRunr that is about to bite you: your first production setup, the database under load, or a retry that does damage twice. You leave with a checklist you can hand to your team, the code from the session, and the option to have the software architecture around your jobs reviewed for free.
Upcoming sessions
Can't make it live? Register anyway. The recording goes out to everyone who signed up the next morning.
JobRunr Foundations · 60 minutes, live
Jobs That Do Not Bring Down Your Database · 60 minutes, live
Scaling JobRunr Under Load · 60 minutes, live
Durable Jobs You Can Trust · 60 minutes, live
No dates on the calendar right now. Register on a training page and you get the next one by email.
Pick your training
Start with Foundations if JobRunr is new to you. The others are for teams that already run it: one on keeping the database alive, one on scaling when the load goes up, one on retries that never do damage twice.
JobRunr Foundations
From your first background job to a production setup, in one hour.
Next:
See the agenda and register →Jobs That Do Not Bring Down Your Database
Background jobs and online traffic on one database, without one slowing down the other.
Next:
See the agenda and register →Scaling JobRunr Under Load
From one server to a fleet, without rewriting a single job.
Next:
See the agenda and register →Durable Jobs You Can Trust
Retries that never charge a customer twice.
Next:
See the agenda and register →How it works
Tell us your problem when you register
One question on the form: what are you trying to do with background jobs right now? The examples in the session come from those answers, so there is a fair chance your case ends up on screen.
Watch it built live
Fifty minutes of live coding in a real application, ten minutes for your questions. Miss it and the recording is in your inbox the next morning.
Get your job architecture reviewed, free
Afterwards you can book thirty minutes on the software architecture around one real job from your codebase. You get a written one-pager with what to change, which you can forward to your team or your architects.
If you set the standard for background jobs
You are not the one who attends. Your tech leads are. What you get is the paper trail.
Send the tech leads
Each one registers, picks the training that matches the system they own, and gets the recording and the checklist. Nothing to procure, nothing to approve.
Get the review in writing
After the training they book an Architecture Review on one real job design. The one-page recommendation that comes back is written for the review board: situation, issues, what to change, and whether the fix is in the design or in a product.
Turn the checklist into your pattern
The production checklist from Foundations is the start of an approved pattern for background jobs: one way to run them, across every team, including the contractors.
After the training: the Architecture Review
The training covers how JobRunr works. The review is about your system: the nightly run that keeps growing, or the retry that once charged somebody twice. Thirty minutes on one problem, then a one-page write-up with what we would change. Free for everyone who attended a training.
What happens in an Architecture Review →Questions