Redis

Job Lab does a lot when nobody is looking: fetching feeds, indexing, sending email and alerts, computing stats, drafting the newsletter, running AI curation. All of it goes through BullMQ queues on Redis, fifteen of them, with 22 scheduled jobs whose timings the admin can change. Redis also holds the login lockout counters, the rate limits and the daily quota for Google's Indexing API.

Each site on a shared server uses its own Redis database number, so their queues never mix.

Worth knowing#

• The app starts without Redis, but with no background jobs, email sent inline and rate limits open, and the health endpoint reports it. Treat it as required.

• Local Lab and Launch Lab have no Redis; their background work is threads and a cron line.