pusher-js VS requests-futures

Now let's push the notification to pusher. First you have to go to https://pusher.com/ login create an app an get API keys. Then fill them in your .env file

another tool is pusher but have a high cost https://pusher.com/

Pusher specializes in realtime WebSockets and offers a straightforward way to integrate realtime features into your React app. It's a reliable choice for apps that need to send notifications based on realtime events.

why are you considering building your own websocket service instead of using something like https://pusher.com/ ?

IVS offers chat rooms, but Kick doesn't seem to use them. All chat messages are sent over a websocket connection to Pusher. Pusher seems pretty cheap for the purpose.

Serveless Websocket service

Is it possible to use Supabase as a Pusher alternative?

if you are on time, since it is a coursework, and it is allowed to use some libraries, you can check how to use pusher it should be fairly easy for you too integrate to your application.

I've built a flutter web chat using flutter_chat_ui and dart_pusher_channels, for the backend I used soketi which is an open source node.js pusher replacement but you could just use pusher.com if you can squeeze into their free tier.

What? No. Takes 5-10 minutes to set up a websocket server manually or is just requires a few configuration variables to be set if using a hosted service like Pusher.

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

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

Lately I tried https://github.com/ross/requests-futures and it is really nice little wrapper for requests library that makes it run asynchronous via thread pool. Worth checking out if you are already using requests lib.

requests-futures can handle that

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).

I would suggest using a session in requests if you're not already but also to look at asyncio/aiohttp , requests-futures or requests-html which can be used asynchronously and is written by the author of the requests library.