Mercure: A WebSocket alternative for server-sent events

1. Mercure

   1 22 4,869 8.7 Go

   🪽 An open, easy, fast, reliable and battery-efficient solution for real-time communications

   

   The site offers a little more detail:

   https://mercure.rocks/

   Basically its server sent events with some stuff on top:

   https://developer.mozilla.org/en-US/docs/Web/API/Server-sent...

   One big benefit of SSE is that you can put them behind a CDN, making scaling a lot easier. No idea about what Mercure brings there, though.

2. CodeRabbit

   coderabbit.ai featured

   CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

   

3. nchan

   2 3 3,036 6.7 C

   Fast, horizontally scalable, multiprocess pub/sub queuing server and proxy for HTTP, long-polling, Websockets and EventSource (SSE), powered by Nginx.

   

   Also I could recommend https://github.com/slact/nchan. It has the same idea: hide and abstract pubsub complexity for a backend service. nchan is built on top of nginx and could be more convenient (existing nginx configuration knowledge) to deploy.

4. feedapi-spec

   3 2 3 1.7

   Specification of the FeedAPI protocol, and links to libraries available.

   

   The specification appears to be very similar to FeedAPI which I have been involved with:

   https://github.com/vippsas/feedapi-spec

   Our focus was kind of the opposite though: Remove the event broker instead of adding one.

   If I understand correctly, Mercure allows you to push events to the broker and clients pull log-based events.

   With FeedAPI we focused instead of removing the broker (RabbitMQ/Kafka/...) and let clients pull log-based events directly from backends. Works wonderfully (at a certain scale).

Suggest a related project