jsynchronous
Centrifugo
jsynchronous | Centrifugo | |
---|---|---|
12 | 31 | |
117 | 7,944 | |
- | 1.6% | |
4.0 | 8.9 | |
about 2 months ago | 10 days ago | |
JavaScript | Go | |
BSD 2-clause "Simplified" License | Apache License 2.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.
jsynchronous
-
Ask HN: What is something you built but never marketed?
A data-synchronization library for Node.js
https://github.com/siriusastrebe/jsynchronous
Ever get tired of sending API requests and JSON payloads? Wouldn't it be cool if data just synced between server and client?
Jsynchronous lets you share deeply nested object/arrays between node.js and connected browsers – and any changes made to that variable.
-
Woe be onto you for using a WebSocket
For the very reasons listed in the article, I built:
https://github.com/siriusastrebe/jsynchronous
a library for keeping a javascript variables synchronized between Node.js servers and clients.
Websockets work great for message passing but it struggles with data structures more complicated than what JSON can represent. Jsynchronous syncs any javascript object or array with arbitrarily deep nesting and full support for circular data structures.
If a computer goes to sleep, or disconnects, websocket connections (and their underlying TCP connections) get reset so you lose any data sent while a computer is unavailable. Jsynchronous will re-send any data clients are missing.
There's also a history mode that lets you rewind to past states.
- Easily share fast changing server data with Jsynchronous.js - for games and real time apps.
- Easily share fast changing server data with Jsynchronous.js - for games and real time apps
- Show HN: Synchronize your rapidly changing app state with all connected browsers
-
Event Sourcing
I recently built https://github.com/siriusastrebe/jsynchronous which uses event sourcing to synchronize javascript variables on the server with connected browsers.
You can also replay states using a special “rewind” mode, a core advantage of event sourcing.
-
5000x faster CRDTs: An Adventure in Optimization
Not for rust - for javascript: Take a look at this library: https://github.com/siriusastrebe/jsynchronous
-
Ask HN: Who wants to be hired? (August 2021)
Fullstack web developer, data visualization and real-time app specialist
I recently built and open sourced https://github.com/siriusastrebe/jsynchronous a real-time data sync library for javascript.
Location: Seattle, full time roles
- Jsynchronous.js - Data synchronization for games and real-time web apps
Centrifugo
-
WebSockets vs. Server-Sent-Events vs. Long-Polling vs. WebRTC vs. WebTransport
Hello, I am author of https://github.com/centrifugal/centrifugo. Our users can choose from WebSocket, EventSource, WebTransport (experimental stabilize in the future). WebRTC is out of scope as the main purpose is central server based real-time json/binary messaging, and WebRTC makes things much more complex since it shines for peer-to-peer and rich media communications.
What I'd like to add is that Centrifugo also supports HTTP-streaming – not mentioned by the OP – but this is a transport which has advantages over Eventsource - like possibility to send POST body on initial request from web browser (with SSE you can not), it supports binary, and with Readable Streams browser API it's widely supported by modern browsers.
Another thing I'd like to mention about Centrifugo - it supports bidirectional WebSocket fallbacks with EventSource and HTTP-streaming, and does this without sticky sessions requirement. I guess nobody else have this at this point. See https://centrifugal.dev/blog/2022/07/19/centrifugo-v4-releas.... Which solves one more practical concern. Sticky sessions is an optimization in Centrifugo case, not a requirement.
If you are interested in topic, we also have a post about WebSocket scalability - https://centrifugal.dev/blog/2020/11/12/scaling-websocket - it covers some design decisions made in Centrifugo.
- Centrifugo v5.1.0 released, with new powers for real-time messaging tasks, now with proxy GRPC subscription streams – similar to WebSocketd but over the network
-
Integrating websockets into my current app
Check out https://github.com/centrifugal/centrifugo - it was initially designed to be a standalone language-agnostic real-time messaging server. So it may be used with Django without radical change in the existing application and using ASGI. It can also provide a much better performance if you care about it.
- Millions of Active WebSockets with Node.js
-
Show HN: DriftDB is an open source WebSocket back end for real-time apps
https://github.com/centrifugal/centrifugo
It's a complete solution, including server, admin panel and client library.
We're an European company and use OVH, Hetzner and others.
-
Laravel Websockets vs Soketi vs Laravel Echo Server
Hello! Theoretically you can take a look at https://github.com/centrifugal/centrifugo - which is a standalone self-hosted real-time messaging server. It does not have native support for Laravel and not compatible with Pusher protocol, though integrating with any backend system, including Laravel: see the blog post https://centrifugal.dev/blog/2021/12/14/laravel-multi-room-chat-tutorial, also has some helper packages:
-
Is Python a good option to implement Websockets?
Hello, it's also possible to design an app in a way that its core will be built with Python, but WebSocket part delegated to something external and efficient like https://github.com/centrifugal/centrifugo – the benefit of the approach is that application business logic is completely decoupled from the real-time transport layer. This may lead to a scalable design with graceful degradation. I think this is especially useful when you already have backend built with Django and need to handle millions of concurrent connections.
- Centrifugo – real-time messaging server (WebSocket, etc.) which scales well and integrates with any backend. SDKs for browser and mobile development included
-
What is the coolest Go open source projects you have seen?
Centrifugo https://centrifugal.dev/ https://github.com/centrifugal/centrifugo
- Golang updating the front-end with almost real-time events from the backend server
What are some alternatives?
QuestJS - A major re-write of Quest that is written in JavaScript and will run in the browser.
Socket.io - Realtime application framework (Node.JS server)
wshook - Easily intercept and modify WebSocket requests and message events.
NATS - Golang client for NATS, the cloud native messaging system.
FluidFramework - Library for building distributed, real-time collaborative web applications
Confluent Kafka Golang Client - Confluent's Apache Kafka Golang client
plumber - A swiss army knife CLI tool for interacting with Kafka, RabbitMQ and other messaging systems.
Mercure - 🪽 An open, easy, fast, reliable and battery-efficient solution for real-time communications
zotonic - Zotonic - The Erlang Web Framework & CMS
laravel-websockets - Websockets for Laravel. Done right.
FASTER - Fast persistent recoverable log and key-value store + cache, in C# and C++.
soketi - Next-gen, Pusher-compatible, open-source WebSockets server. Simple, fast, and resilient. 📣