3 ms·

I imagine that Supabase would be a perfect candidate for this project! I would love to get the authors opinion on it too.

typingmonkey 5y ago
I considered to add Supabase, RethinkDB and meteor. But they are not really client side databases. They realtime stream query results from the server to the client.
- knes 5y ago
  Did you look into https://ditto.live/ https://ditto.live/? Its and off-line first db too. I never used it but looks very interesting and would be interested how it compare to the technologies you picked
- irae 5y ago
  I love RethinkDB. I really believe it is a database that deserves more attention. We've been running on it for six years and it is flawless, easy to use. Like any other database you need to understand how it performs and how to query efficiently. But it does has everything required for streaming and syncing data in a modern way. You can open streaming queries and even with a backlog of data, so syncing should be pretty easy. Maybe would be feasible to fork PouchDB to use RethinkDB as a backend?
- PKop 5y ago
  Firestore isn't really a client side database then either. It is certainly also querying results from a server.
jonplackett 5y ago
I second that! Would like to see supabase since that’s what I’ve been using a lot recently and really liking!
- mastazi 5y ago
  I have a question, how do you manage the fact that Supabase is based on a relational db[1]? Do you just put all fields (except the primary key) in a JSON column[2]? Does it work well if you use it that way? We were investigating it as a way to escape Firebase's vendor lock-in but the fact that we would have to manage schema migrations was a bit of a deal breaker based on our use case. I'm also interested in hearing about any alternatives to Supabase that use a document-based nosql db. [1] https://supabase.io/database https://supabase.io/database [2] https://www.postgresql.org/docs/13/datatype-json.html https://www.postgresql.org/docs/13/datatype-json.html
  - jonplackett 5y ago
    Personably I kinda like the fact that it’s a relational DB. The stuff you gain by having users only allowed to do certain things based on certain fields using Policies makes life a lot easier and more relaxing.
    - mastazi 5y ago
      Firestore can do that, a DB engine doesn't need to be relational to offer that feature. https://firebase.google.com/docs/firestore/security/get-started https://firebase.google.com/docs/firestore/security/get-star...

typingmonkey 5y ago

I considered to add Supabase, RethinkDB and meteor. But they are not really client side databases. They realtime stream query results from the server to the client.

knes 5y ago
Did you look into https://ditto.live/ https://ditto.live/? Its and off-line first db too. I never used it but looks very interesting and would be interested how it compare to the technologies you picked
irae 5y ago
I love RethinkDB. I really believe it is a database that deserves more attention. We've been running on it for six years and it is flawless, easy to use. Like any other database you need to understand how it performs and how to query efficiently. But it does has everything required for streaming and syncing data in a modern way. You can open streaming queries and even with a backlog of data, so syncing should be pretty easy. Maybe would be feasible to fork PouchDB to use RethinkDB as a backend?
PKop 5y ago
Firestore isn't really a client side database then either. It is certainly also querying results from a server.

jonplackett 5y ago

I second that! Would like to see supabase since that’s what I’ve been using a lot recently and really liking!

mastazi 5y ago
I have a question, how do you manage the fact that Supabase is based on a relational db[1]? Do you just put all fields (except the primary key) in a JSON column[2]? Does it work well if you use it that way? We were investigating it as a way to escape Firebase's vendor lock-in but the fact that we would have to manage schema migrations was a bit of a deal breaker based on our use case. I'm also interested in hearing about any alternatives to Supabase that use a document-based nosql db. [1] https://supabase.io/database https://supabase.io/database [2] https://www.postgresql.org/docs/13/datatype-json.html https://www.postgresql.org/docs/13/datatype-json.html
- jonplackett 5y ago
  Personably I kinda like the fact that it’s a relational DB. The stuff you gain by having users only allowed to do certain things based on certain fields using Policies makes life a lot easier and more relaxing.
  - mastazi 5y ago
    Firestore can do that, a DB engine doesn't need to be relational to offer that feature. https://firebase.google.com/docs/firestore/security/get-started https://firebase.google.com/docs/firestore/security/get-star...