⚡
Use case
FastAPI background jobs
Offload email, webhooks, PDF generation, and third-party calls out of the request path with an async client built for FastAPI.
Best for: Teams shipping FastAPI APIs that need to move slow work off the request/response cycle.
The problem
- FastAPI BackgroundTasks run in-process and die with the worker — no retries, no visibility, no horizontal scale.
- Wrapping Celery in an async web app means thread pools and sync bridges just to enqueue a job.
- Standing up Redis plus a result backend plus Flower is heavy for a service that just needs to send some emails.
How FastWorker handles it
- 1 Import the async Client and call await client.delay("send_email", to, body) directly from an endpoint.
- 2 Run the control plane alongside your API and add subworkers as traffic grows.
- 3 Watch queue depth and task history in the built-in dashboard — no extra service.