omnistreams-spec
Mercure
omnistreams-spec | Mercure | |
---|---|---|
2 | 19 | |
7 | 3,741 | |
- | - | |
0.0 | 8.4 | |
over 2 years ago | 10 days ago | |
Go | ||
- | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
omnistreams-spec
-
Server-Sent Events: the alternative to WebSockets you should be using
My personal WebSockets vs SSE TL;DR goes something like this:
* If you're on HTTP/2, start with SSE
* If you need to send binary data, use WebSockets
* If you need fast bidi streaming, use WebSockets
* If you need backpressure and multiplexing for WebSockets, use RSocket or omnistreams[1] (one of my projects).
[0]: https://rsocket.io/
[1]: https://github.com/omnistreams/omnistreams-spec
-
The WebSocket Handbook
I built omnistreams[0] primarily because of the lack of backpressure in browser WebSockets (lots of background information in that README). It's what fibridge[1] is built on. We've been using it in production for over 2 years, but I never ended up trying to push omnistreams as a thing. I believe the Rust implementation is actually behind the spec a bit, and the spec itself probably needs some work.
At the end of the day I think RSocket is probably the way to go for most people, though the simplicity of omnistreams is still appealing to me.
[0]: https://github.com/omnistreams/omnistreams-spec
[1]: https://iobio.io/2019/06/12/introducing-fibridge/
Mercure
-
PHP homies, I hear ya.
Are you aware of things like websockets and mercure.rocks?
-
What is the best way to write a dedicated server?
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.
-
What to use to replace laravel web sockets?
You can try https://mercure.rocks/.
-
OpenAI server-sent events supported chatbot
It's worth looking at something like Mercure , which is used by API Platform
-
laravel activity feed
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.
-
Golang updating the front-end with almost real-time events from the backend server
You can use Mercure https://mercure.rocks/ , Mercure uses http2.
-
Centrifugo v4 released – with own WebSocket emulation layer, optimized client protocol, unified SDK behavior, experimental HTTP/3 and WebTransport support
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.
-
How would I automatically update how much users are signed up for each group?
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.
- Mercure: Real-Time Made Easy
-
Announcing GraphQL Yoga 2.0!
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)
What are some alternatives?
editor - Collaborative text editor using operational transformations
Socket.io - Realtime application framework (Node.JS server)
overture - Overture is a powerful JS library for building really slick web applications, with performance at, or surpassing, native apps.
websocket - A fast, well-tested and widely used WebSocket implementation for Go.
wstunnel - Tunnel all your traffic over Websocket or HTTP2 - Bypass firewalls/DPI - Static binary available
Centrifugo - Scalable real-time messaging server in a language-agnostic way. Self-hosted alternative to Pubnub, Pusher, Ably. Set up once and forever.
stable-socket - A web socket that reconnects.
amqp091-go - An AMQP 0-9-1 Go client maintained by the RabbitMQ team. Originally by @streadway: `streadway/amqp`
dom-examples - Code examples that accompany various MDN DOM and Web API documentation pages
NATS - Golang client for NATS, the cloud native messaging system.
sarama - Sarama is a Go library for Apache Kafka. [Moved to: https://github.com/IBM/sarama]
gorush - A push notification server written in Go (Golang).