Thirty minutes on your job design
The training teaches the mechanics. The Architecture Review is where we look at your actual system: the jobs you run, the database underneath, the ways it fails. You leave with a written recommendation you can put in front of your team or your architects.
How a review goes
You bring one problem
One job or one flow, not the whole platform. The nightly run that keeps growing, the retry that once did damage, the batch that stalls the database. Send a short description when you book, so we can prepare.
We go through it together
Thirty minutes on a call with Ronald Dehuysser or Nicholas D'hondt. Screen sharing welcome. We ask how it works today, where it hurts and what it has to do in a year. Classic solution architecture, no demo.
You get it in writing
Within a week you receive a one-page summary: the situation as we understood it, the issues we see, and our recommendation. Sometimes that is a JobRunr feature. Often it is a change in how the job is designed, and we say so.
✓ What we ask
- ✓ That you attended one of the trainings, live or on the recording
- ✓ A short description of the problem when you book
- ✓ Permission to use what we learn, anonymised, to improve JobRunr
✗ What we never do
- ✗ Turn the call into a sales pitch
- ✗ Recommend JobRunr Pro when the fix is in your design
- ✗ Share anything about your system with anyone
Who should take the review
The developer who owns the jobs, together with whoever signs off on the architecture, if that is a different person. Reviews go best when both are on the call: one knows what the code does, the other knows what it has to guarantee.
How to book
The booking link opens in the last five minutes of every training and is in the email with the recording. If you attended and lost the link, email nicholas@jobrunr.io with the training you joined.
See upcoming trainings