Socket.io VS Mercure

5. Socket.io

Socket.io: Real-time communication used by the application to provide live update of some feature and settings.

Websockets in Node.js There are various libraries that let you create a ws server:- https://www.npmjs.com/package/websocket https://github.com/websockets/ws https://socket.io/

For the socket integration I use https://socket.io/ and follow their integration guide about nextjs ( https://socket.io/how-to/use-with-nextjs)

Wasp has lots of time-saving features, including WebSocket support via Socket.IO, Authentication, Database Management, and Full-stack type-safety out-of-the box.

I don’t like to use sockets on nextjs, just looking at the integration page of socket.io (How to use with Next.js | Socket.IO) feel so weird for me, also combining the fact that the developer server is just a nightmare, I prefer to avoid everything related to websockets and nextjs at least for the moment.

Repository: Socket.io

When developing web applications, you might encounter connectivity issues between your client and server when using Socket.io on localhost.

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)