requests-futures VS django-channels

- https://github.com/ross/requests-futures

For the simple one-off case, check out requests-futures or requests-threads

Thank you, I didn’t know about this before. Looks like either requests-threads or requests-futures can do the job. Not sure how I can add async and await to the script above, I’ll tinker around with it later!

I found examples of running parallel async http requests using grequests, but in its GitHub page it recommends using requests-threads or requests-futures instead. Which of them would be the most straightforward tool for optimizing a sequence of GET requests against an API. Case scenario: API endpoint provides paginated responses. With first response, I get the total of itens, which allow me to prepare all the remaining urls. The API allows for 25 simultaneous requests from a single user session (JWT token).

WebSockets or MQTT. If you’re open to Python and Django as a framework, check out Django Channels.

Use Django channels package. I'm not very convinced for these reasons:

github issue

One program I sorta like is channels. You may have some luck searching for python example repositories (IIRC there is at least one project like this, with the structure and explaining what each stuff does, give preference to more recent projects as packaging is something that went through a lot of changes in the recent years).

This is my first post, and I am sharing the experience of using Django Channels for a couple of our products, which are both live, one(legacy product) still running django channels and another deployed at AWS API Gateway using Websockets API.