hist-prototype VS peerjs

I have 2 projects that I'm looking to eventually adapt into a database backend that's API compatible with RocksDB (with enhancements!). The first of which is a Extendible Hashing Implementation in Rust (it was my first attempt at Rust, so it's kinda messy): https://github.com/chiefnoah/MehDB

It achieves very promising performance for u64 sized types (which will eventually be an offset into a log).

The other is a similar concept using modified B+Trees that have subtrees for all writes to a record: https://github.com/chiefnoah/hist-prototype

This one is implemented in Python for fast iteration, as I realized I wasn't happy with how fast I could iterate with Rust. This one is, IMO, a more complete approach towards full historical query-capable systems. I'm slowly chipping away at it, though I haven't had progress lately. I spend no real money to host them, just the code, though I'm certain I've shortened the life of my NVMe drives due to writing and rewriting large files for testing.

this app is using peerjs to connect peers over a webrtc connection. check out thier docs for more info. with webrtc, things like file-transfer, should be very performant compared to cloud storage providers... especially over LAN. network speed doesnt seems to be an issue i have experienced.

I'm using the client-side PeerJS https://peerjs.com/ library for networking. As the name may imply, a direct connection is established between two peers using WebRTC via "handshake" through an intermediary server they host - and, they provide source for the server as well. I have found it to be quite reliable, thus far.

You kind of sound like a beginner. The browser APIs are a bit painful to work with. It might be easier to use PeerJS: https://peerjs.com/

If you want you can use Preact. PreactJS is a lightweight alternative to ReactJS, designed for high performance and compatibility. is often used in applications where performance is critical and has a small footprint.

This opens up a lot of neat possibilities, and fortunately I found a very easy JavaScript library for handling multiplayer called PeerJS. The way you can send packets from player to player is very simple and something even a beginner to JavaScript could understand.

You might be able to eliminate the VPS by making it P2P using something like PeerJS [1]. PeerJS provides a free shared connection broker server.

[1]: https://peerjs.com/

Note: peerjs is a good starting point!

We use peer.js module to create a WebRTC connection between clients

Now that we have all the required boilerplate we can start building the actual game. For the communications between peers we are going to use PeerJS a peer-to-peer library built on top of WebRTC.