jsynchronous VS FASTER

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

You would be surprised by performance of modern .NET :)

Writing no-alloc is oftentimes done by reducing complexity and not doing "stupid" tricks that actually work against JIT and CoreLib features.

For databases specifically, .NET is actually positioned very well with its low-level features (intrisics incl. SIMD, FFI, struct generics though not entirely low-level) and high-throughput GC.

Interesting example of this applied in practice is Garnet[0]/FASTER[1]. Keep in mind that its codebase still consist of un-idiomatic C# and you can do way better by further simplification, but it already does the job well enough.

[0] https://github.com/microsoft/garnet

[1] https://github.com/microsoft/FASTER

A vaguely similar project that might be of interest is: https://github.com/microsoft/FASTER

It's also an "unbundled" low-level component that one could use as the foundation for a database engine or whatever. According to Microsoft, FASTER is not just "fast", but significantly faster than even some basic in-memory data structures that ship in the .NET standard library!

The downside is that it doesn't (yet) support some more advanced features like multi-server distributed mode.

However, that relative simplicity may be preferred in some scenarios...

Last time i looked into it there weren't that many i could find. There is https://github.com/tikv/tikv which uses rocksdb with raft. and there is faster https://github.com/microsoft/FASTER/ .

you could use fasterkv https://github.com/microsoft/FASTER

FTA, https://github.com/Microsoft/FASTER/wiki/Performance-of-FAST...