Your API should not wait on Twilio or an inbox provider
A user signs up and you need a text and a welcome email. The handler should answer fast. The send can take seconds, fail, or retry while your HTTP thread sits there.
FastAPI RabbitMQ Celery Flower Starter is the lab that already wires the split: an API that enqueues work, workers that call providers, persistence for status, and dashboards you can open on localhost.
Accept the job. Let workers carry the slow part.
What you get
- Fast HTTP, slow work elsewhere. REST endpoints trigger notification jobs without blocking on provider round trips.
- SMS and email on separate queues. Text and mail do not fight for the same lane when traffic spikes.
- Tracked message status. A database records what was sent so you are not guessing from logs alone.
- Visibility while you learn. Broker and worker dashboards start with the compose stack for local debugging.
- Free AGPL starter. Separate web and worker code you can change, plus a Next.js client added in v1.1.0 for template previews.
Your first morning after cloning
You bring Twilio and Brevo credentials into the web and worker env files, start the stack, and open the interactive API docs. You enqueue a test SMS and a test email. RabbitMQ shows two queues. Flower shows tasks moving. Postgres holds status rows. That loop is the reference before you harden retries, rate limits, or compliance for production.






