FastAPI Background Tasks — ELI5

You walk into a restaurant and order a burger. The waiter writes down your order, hands you a number, and says “it’ll be ready at the counter.” You sit down. The kitchen starts cooking.

Notice what happened: the waiter didn’t disappear into the kitchen to cook your burger personally. They gave you an answer right away (“here’s your number”) and the cooking happened separately.

That’s what background tasks are in FastAPI. When someone sends a request to your web app — like “send a welcome email to this new user” — your app doesn’t have to finish sending the email before responding. It can say “got it, user created!” immediately, and then send the email in the background.

Why does this matter? Because sending an email might take two or three seconds. If your app waited that long before responding, the person waiting would be staring at a loading spinner. Nobody likes that.

With background tasks, the slow stuff happens after the response is already on its way. The user gets their answer fast, and the behind-the-scenes work finishes on its own time.

There’s a catch though: if your app crashes before the background task finishes, that task is lost. It’s like the kitchen catching fire before your burger is done — nobody’s finishing that order. For truly important work, you need something more reliable. But for things like sending notifications or cleaning up temporary files, background tasks are perfect.

The one thing to remember: Background tasks let your app respond immediately and handle slow work afterward — like a waiter taking your order while the kitchen cooks in parallel.