pusher-js VS laravel-websockets

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.

I'm working on a real-time chat application but facing some issues while working with broadcasting events using the laravel-websockets package. Things were working fine yesterday and I was receiving messages from private and public channels but I don't know why I'm not receiving messages anymore.

Yes I did and even found that documentation but I just wanted to confirm that I'm on the right track. Do you suggest using Laravel-Websockets or Pusher as a broadcaster? I am inclined to use Laravel-Websockets just because it's free (so I wouldn't have recurrent costs), however I don't want to end up with limitations or issues later on.

Laravel Echo is free and part of Laravel. You need to use it with a websockets server or a service like Pusher or Ably, and that is what you pay for. But if you make your own websockets server with Laravel Websockets, as u/phoogkamer suggested, you can host your own websockets server on your infrastructure.

Laravel Websockets

I'm using beyondcode/laravel-websockets with laravel/echo on localhost. Public channels work fine, I also tested private channels by giving productId manually and it works.

https://github.com/beyondcode/laravel-websockets is an OSS Pusher implementation. /u/serenityphp