jsynchronous VS message-db

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.

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.

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.

Not for rust - for javascript: Take a look at this library: https://github.com/siriusastrebe/jsynchronous

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

I’m addition to the alternatives mentioned, here’s another Postgres-only ES implementation: https://github.com/message-db/message-db

Thalo is a new Rust library that provides a runtime for WASM-based event sourcing. With Thalo, developers can compile their aggregates and components into WASM modules and use them in the runtime to handle commands and persist events to an event store. The library is built on top of Wasmtime and Message DB, and uses the ESDL schema language to define aggregates. While Thalo is not yet ready for real-world use, it has the potential to make event sourcing more accessible to a wider range of languages that compile to WASM, allowing for a language-agnostic runtime. Give it a try and let us know what you think! https://github.com/thalo-rs/thalo

Its built on top of Wasmtime for wasm execution, and MessageDb which is a message store for Postgres.

We are using message db which is uses postgres under the hood, and provides a few useful postgres functions. We use it with `postgres-simple` and have a small internal library. However my colleague is working on abstracting our logic and open sourcing into a library here: https://github.com/Disco-Dave/message-db

Check out MessageDB https://github.com/message-db/message-db. It's basically Postgres and can be installed into any Postgres DB.

Trying a new language or framework is fun experiments that you spend a few hours on. I have been enjoying implementing Message DB[0] in a hobby project. My current job is not in programming, and not looking for one.

[0]https://github.com/message-db/message-db