A database trigger notifies Solid Queue workers the moment a job becomes ready, so jobs start in milliseconds even with polling intervals raised to seconds or minutes — which cuts the idle query load that polling generates by orders of magnitude. No monkey patches: the gem wires itself in through Solid Queue's documented lifecycle hooks. Polling remains the correctness backstop, and every failure mode — missing trigger, non-Postgres adapter, PgBouncer, a dropped connection, a fork — degrades loudly to stock Solid Queue behavior.