5 ms·

This is really neat, I have been keeping an eye on Supabase, this (presence) is the feature that will finally push me to build a side project with it. I have on

This is really neat, I have been keeping an eye on Supabase, this (presence) is the feature that will finally push me to build a side project with it. I have one in mind. Anyone from Supabase here, do you have any plans to build in support for CRDT toolkits such as Yjs or AutoMerge for these features? It would make working with them so much easer if there was a plug and play backend. The one other thing I would love to see next from them is an offline sync product, so you could partially sync a users dataset to their device and save back any changes later (bonus points for then combing that with CRDTs). Maybe the WASM Postgres yesterday [0] could be a foundation for such a product. https://news.ycombinator.com/item?id=32498435 https://news.ycombinator.com/item?id=32498435

Xeoncross 4y ago
Agree, I would love to see CRDT (or related) multiplayer resolution as that's a big time sink for a lot of new collaboration product ideas around dashboards, documents, spreadsheets, online games, mindmaps, and flows (like figma).
danielvaughn 4y ago
Yeah this actually confused me a bit - at first I thought "multiplayer" meant CRDT, but now I'm not sure. I got really excited there for a bit, lol.
kiwicopple 4y ago
> CRDT It's definitely something we'll support (we mention it briefly in the blog post). We'll extend this service so that it works well with WebRTC, and we have a few ideas for making it easy for development. > Maybe the WASM Postgres yesterday This was mind-blowing! Very cool what the crunchy team have done there. It would be awesome to replicate from a remote Postgres database to a "per-user" database to the browser. I think WASM support needs to improve before it can become generally useful for offline-sync, but the tech seems withing reach. We're working on various ideas for offline-sync, but the Realtime server will be central to whatever implementation we land on.
- samwillis 4y ago
  Both of those sound super exiting! I previously experimented with building an offline syncing CRDT db using Pouch/CouchDB and combining it with Yjs for automatic conflict resolution. But Postgres would be so much better as the foundation. If only I had time it is something I would love to work on…
  - kiwicopple 4y ago
    perhaps we can help you find some time (contact details are in my profile)
- pcthrowaway 4y ago
  Any idea if Realtime might support Postgres streaming replication in the future? We were incredibly excited to use Realtime with TimescaleDB, but couldn't get it working. I assumed it was related to https://docs.timescale.com/timescaledb/latest/how-to-guides/replication-and-ha/about-ha/#replication https://docs.timescale.com/timescaledb/latest/how-to-guides/... (even though we were only running it single-node, my understanding is that Realtime works by tapping into the replication feed)
  - kiwicopple 4y ago
    Realtime uses logical replication, and from your link it looks like it should work with Timescale (although not recommended): > Using logical replication with TimescaleDB is not recommended, as it requires schema synchronization between the primary and replica nodes and replicating partition root tables, which are not currently supported. As long as logical replication is supported, this won't be an issue for Realtime because the purpose is to receive data changes (which come in a JSON format) and the end-user doesn't need to persist schema modifications. > but couldn't get it working If you send me some error logs, I can take a look or forward to one of the team. > support Postgres streaming replication This is the first time I've heard it requested - I don't think it's something we'd do unless there was a good reason and strong demand. If we were to do any work in this direction we'd prefer to try contribute DDL streaming to PostgreSQL's logical streaming. We've been thinking about this for a while (Michel has built metagration - https://github.com/michelp/metagration https://github.com/michelp/metagration which has prompted a few ideas for core patches)

Xeoncross 4y ago

Agree, I would love to see CRDT (or related) multiplayer resolution as that's a big time sink for a lot of new collaboration product ideas around dashboards, documents, spreadsheets, online games, mindmaps, and flows (like figma).

danielvaughn 4y ago

Yeah this actually confused me a bit - at first I thought "multiplayer" meant CRDT, but now I'm not sure. I got really excited there for a bit, lol.

kiwicopple 4y ago

> CRDT It's definitely something we'll support (we mention it briefly in the blog post). We'll extend this service so that it works well with WebRTC, and we have a few ideas for making it easy for development. > Maybe the WASM Postgres yesterday This was mind-blowing! Very cool what the crunchy team have done there. It would be awesome to replicate from a remote Postgres database to a "per-user" database to the browser. I think WASM support needs to improve before it can become generally useful for offline-sync, but the tech seems withing reach. We're working on various ideas for offline-sync, but the Realtime server will be central to whatever implementation we land on.

samwillis 4y ago
Both of those sound super exiting! I previously experimented with building an offline syncing CRDT db using Pouch/CouchDB and combining it with Yjs for automatic conflict resolution. But Postgres would be so much better as the foundation. If only I had time it is something I would love to work on…
- kiwicopple 4y ago
  perhaps we can help you find some time (contact details are in my profile)
pcthrowaway 4y ago
Any idea if Realtime might support Postgres streaming replication in the future? We were incredibly excited to use Realtime with TimescaleDB, but couldn't get it working. I assumed it was related to https://docs.timescale.com/timescaledb/latest/how-to-guides/replication-and-ha/about-ha/#replication https://docs.timescale.com/timescaledb/latest/how-to-guides/... (even though we were only running it single-node, my understanding is that Realtime works by tapping into the replication feed)
- kiwicopple 4y ago
  Realtime uses logical replication, and from your link it looks like it should work with Timescale (although not recommended): > Using logical replication with TimescaleDB is not recommended, as it requires schema synchronization between the primary and replica nodes and replicating partition root tables, which are not currently supported. As long as logical replication is supported, this won't be an issue for Realtime because the purpose is to receive data changes (which come in a JSON format) and the end-user doesn't need to persist schema modifications. > but couldn't get it working If you send me some error logs, I can take a look or forward to one of the team. > support Postgres streaming replication This is the first time I've heard it requested - I don't think it's something we'd do unless there was a good reason and strong demand. If we were to do any work in this direction we'd prefer to try contribute DDL streaming to PostgreSQL's logical streaming. We've been thinking about this for a while (Michel has built metagration - https://github.com/michelp/metagration https://github.com/michelp/metagration which has prompted a few ideas for core patches)