I’m building a Telegram bot that’s expected to handle about 100 users per day. I’m not sure if I need to use a task queue like Redis or if the bot can handle requests on its own.
I tried setting up a Redis queue for user commands:
task = job_list.add(create_new_key, user_id)
while not task.completed:
result = task.get_result()
time.sleep(1)
But when I tested the bot with and without the queue, I couldn’t see any difference. My buddy and I tried using commands at the same time, and both versions seemed to handle tasks similarly.
Does anyone know if a task queue is really needed for a Telegram bot with this kind of traffic? Or can the bot handle concurrent requests on its own? I’m confused about the best way to structure this. Any advice would be great!
From my experience working with Telegram bots, I’d say a task queue isn’t strictly necessary for your use case. With only about 100 users per day, a well-structured bot should be able to handle concurrent requests without significant issues.
I’ve built several bots handling similar traffic, and they’ve performed just fine without a queue. The key is to ensure your code is efficient and non-blocking where possible. Use async functions for I/O operations, and consider using a library like aiogram which is designed for asynchronous bot development.
That said, a task queue can be beneficial if you have long-running tasks or need to ensure perfect order of execution. But for most basic bot functionalities, it’s often overkill at your scale.
If you’re not seeing performance benefits with the queue, I’d suggest focusing on optimizing your bot’s code structure first. You can always add a queue later if you start seeing performance issues as your user base grows.
hey charlotte, from wat i see, u probably dont need a queue for ur bot. i’ve made bots handling way more users without one. the telegram api is pretty good at handling multiple requests.
but if ur doing heavy stuff like image processing, a queue might help. otherwise, keep it simple and add one later if u need it.
In my professional opinion, a task queue isn’t essential for your Telegram bot at this scale. I’ve developed bots handling thousands of daily users without queues. The Telegram API is robust enough to manage concurrent requests efficiently.
However, if you’re implementing resource-intensive operations or need strict task ordering, a queue could be beneficial. For your current needs, I’d recommend focusing on optimizing your code structure and utilizing asynchronous programming techniques.
Monitor your bot’s performance as it grows. If you start noticing bottlenecks or delays in response times, then consider implementing a task queue. Until then, keep your architecture simple and scalable.
Remember, premature optimization can often lead to unnecessary complexity. Build for your current needs, but design with future scalability in mind.