Title: Hey HN! I’ve written a bunch of WebSocket servers over the years to do simple things like state synchronization, WebRTC signaling, and notifying a client when a backend job was run. I realized that if I had a simple way to create a private, temporary, mini-redis that the client could talk to directly, it would save a lot of time. So we created DriftDB.<p>In addition to the open source server that you can run yourself, we also provide <a href="https:&#x2F;&#x2F;jamsocket.live" rel="nofollow">https:&#x2F;&#x2F;jamsocket.live</a> where you can use an instance we host on Cloudflare’s edge (~13ms round trip latency from my home in NY).<p>You may have seen my blog post a couple months back, “You might not need a CRDT”[1]. Some of those ideas (especially the emphasis on state machine synchronization) are implemented in DriftDB.<p>Here’s an IRL talk I gave on DriftDB last week at Browsertech SF[2] and a 4-minute tutorial of building a cross-client synchronized slider component in React[3]<p>[1] <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=33865672" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=33865672</a><p>[2] <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=wPRv3MImcqM">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=wPRv3MImcqM</a><p>[3] <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=ktb6HUZlyJs">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=ktb6HUZlyJs</a>
Upvote: