DriftDB

Dev tools

realtime backend

SHOW HN2023

367points
101comments
#102of 3,109 in 2023
Top 4%of 2023 by points

How HN took it

MixedNo clear lean

15 positive, 23 neutral or asking, 1 mixed, 8 critical, out of 47 comments about the project. Thread score +0.13.

Idea: 5 for, 4 againstDocs: 2 for, 1 againstPricing: 0 for, 2 againstPerformance: 1 for, 1 againstDesign: 1 for, 0 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Useful for real-time multiplayer and sync use cases

    From 2 comments
    • This is great. I'm going to use this with something I'm working on. The edge behavior is just what I need. When you say limitations are a "relatively small number of clients need…
      BTBurke on HN
    • This looks just about perfect for powering all those team online games we all played a lot during lockdown (and still do), is that right?
      globalise83 on HN

Objections

  • Name suggests persistence but it is not a database yet

    From 1 comment
    • Would be fascinating if you could build Jitsi like video ontop of this. I think DB in the name is a little misleading due to there being no persistence (I assume?) but that is a…
      quickthrower2 on HN
  • Unclear what edge means and how multiple instances share state

    From 2 comments
    • Neat. > DriftDB is a real-time data backend that runs on the edge What does it mean for these backends to be “on the edge”? Do geographically disperse clients connect to…
      rlt on HN
    • > DriftDB is a real-time data backend that runs on the edge. What does "on the edge" mean in this context? Can I just run the server part on my own infrastructure? What if I have…
      matt-attack on HN
  • Websocket latency makes real-time guarantees impossible

    From 1 comment
    • How can something be real-time, if there is a websocket connection in-between. How do you ensure real time? In real-time applications response times must be guaranteed. Seems…
      Aldipower on HN

Requests

  • Persistence for long-lived rooms

    From 1 comment
    • > but what about the time factor? Can it be on the order of hours? So far I’ve focused on use cases where clients are online for overlapping time intervals. When all the clients…
      paulgb on HN
  • Dart/Flutter support

    From 1 comment

Questions

  • Why not MQTT or a standard protocol

    From 1 comment
    • I've not looked at DriftDB in depth (cloudflare worker running this is neat!), but can't MQTT handle this sort of workload? Obv. there's not a cloudflare worker running say an…
      alexisread on HN
  • How race conditions are handled

    From 1 comment
    • How the race conditions are handled? If one of the clients of the shared state delivers the the input with a delay(network issue etc.), will it overwrite state of the other…
      mrtksn on HN

Alternatives named

  • NATS

    From 1 comment
    • Nice, have you come across NATS? https://nats.io. The server natively supports WebSockets. There are many clients including Deno, Node, WebSockets, Rust, Go, C, Python, etc. In…
      bruth on HN
  • Colyseus

    From 1 comment
    • Reminds me of Colyseus: https://github.com/colyseus/colyseus
      speps on HN
  • MQTT

    From 1 comment
    • I've not looked at DriftDB in depth (cloudflare worker running this is neat!), but can't MQTT handle this sort of workload? Obv. there's not a cloudflare worker running say an…
      alexisread on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/34639728)