Mercure VS laravel-websockets

Are you aware of things like websockets and mercure.rocks?

It could be implemented with STOMP, or Mercure (goes well with API-Platform, written in PHP/Symfony), you could write your own with the help of nchan and scale it via Redis. If it's a web service, the best practices for operating and scaling are well established, Godot then just becomes another client.

You can try https://mercure.rocks/.

It's worth looking at something like Mercure , which is used by API Platform

Pusher might be one of these systems, Mercure is another one (which you can host yourself). Mercure has good documentation and some examples in various languages, including PHP: https://mercure.rocks/docs/ecosystem/awesome#examples.

You can use Mercure https://mercure.rocks/ , Mercure uses http2.

I actually was thinking about this when I saw https://github.com/dunglas/mercure project to become a Caddy plugin. But I did not find enough reasoning to try this with Centrifugo at that point, and still... Seems awesome from one side - tight integration with a web-server, no extra network between LB and Centrifugo. But will this be useful in practice and find its users? 🤔 That's the question I don't have an answer yet.

Polling is kind of ok (data might change between poll events), but real-time updates are better. So If you don't mind adding an extra service, then take a look at mercure.

Two more questions: - Am I to understand The Guild now recommends GraphQL Yoga over Helix? - Could something like Mercure be included in the recipes ? (this would be a nice solution for serverless)

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