Every real app eventually needs to do work that doesn't fit inside a web request — sending email, calling external APIs, processing uploads, generating reports. If you do that work inline, your user sits there watching a spinner. The answer is background jobs, and the Build New template comes with them already wired up.
In this lesson we'll cover what background jobs are, walk through six common situations where you'd reach for one, compare Solid Queue to the older Sidekiq approach and explain why I chose the simpler option, and confirm that everything is ready to use in the template from day one.
- Why doing slow work in a web request is a bad idea
- Six real-world situations where background jobs are the right move
- Why I use Solid Queue instead of Sidekiq + Redis
- How Solid Queue is already running in the template with zero setup