Socket.io VS Mercure

Web Real-Time Communication (WebRTC) is a technology developed by Google in 2013 for peer-to-peer communication. WebRTC enables web browsers to capture audio, video, exchange data, and teleconferencing without plugins or intermediaries. WebRTC achieve these through APIs and protocols that interact with one another. WebRTC media streaming when used with SocKet.IO will produce an application that streams media and exchange data instantly. Socket.IO is a library that provides low latency bi-directional communication between client and server. Socket.IO was built on websocket, a communication protocol that provides a full-duplex and low latency communication between server and browser. In this article, readers will learn how to build a video chat application using WebRTC and Socket.IO. This article is for web developers who wish to develop web applications that can stream media between two peers of computers in real-time without installing any plugins.

In this article, you'll learn how to build a real-time project management app using React, Socket.IO, and Bryntum Gantt, a powerful tool that can help you easily set up project tasks, track their progress, and collaborate with team members.

Socket.io

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 could use socket.io and run my application in dev mode.... as socket.io works well in dev mode with sveltekit... but not a great option.

Considering it's a text game there is not much you really have to learn except for websockets. Now there are some differences here and there but socket.io will definitely be good enough. It has features for putting users in a specific room, that way you can scope who receives the packets!

socket.io had it's place but it's a bit like jQuery/Moment.js, you probably don't need it for modern apps aside from legacy/experimentation reasons.

socket.io is likely the bottleneck, if node.js is the only option switch to websockets (ws) or better uWebsockets.js pub/sub with redis pub/sub for scaling

How would I go about making a live quiz app similar to that of Gimkit, Kahoot, Quizziz, Quizlet live, etc? From my research, People use socket.io but I have found nothing about using it in an application like this, where one would make a quiz and have people join.

It is a socket.io server implemented as a tower layer in rust so it integrates really well with anything based on tower (Axum,Warp,Hyper). Two other persons started to contribute so I'm really happy.

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)

The Mercure Hub originally dealt with this issue using an in memory cache to eliminate duplicate regular expression evaluations.

There's also the Mercure protocol, built on top of Server-Sent Events: https://mercure.rocks/