How are the messages priced? Are retries free?
How is the Max Message Size Limit applied?
What happens when we hit daily max messages limit?
Videos
I just released Qstash, A message broker between your serverless apps. You send an HTTP request to QStash, that includes a destination, a payload and optional settings. We durably store your message and will deliver it to the destination API via HTTP. In case the destination is not ready to receive the message, we will retry the message later, to guarentee at-least-once delivery.
Features:
100% serverless, no stateful connections required. Messages are pushed to your API.
At-least-once delivery guaranteed to any public API
Pubsub via topics
Delay message delivery
Message deduplication
Scheduling via CRON
Hello guys, I'm currently working on a personal project and would like to know your thoughts and advice on handling background tasks in django.
My use cases includes:
Sending transactional emails in the background
Some few periodic tasks
Celery is super powerful and flexible, but it requires running a persistent worker which can get tricky or expensive on some platforms like Render. On the other hand, QStash lets you queue tasks and have them POST to your app without a worker — great for simpler or cost-sensitive deployments.
Have you tried both? What are the treadoffs of adopting django-Qstash.