A Graph-Based Firebase
stopa.io
A Graph-Based Firebase
1–10 of 53 posts
Re: A Graph-Based Firebase
#2I use Hasura for this purpose. With some hooks, you can achive offline mode, too.
You need a bit tricky hacks to use Hasura permission system the way you want, though.
Re: A Graph-Based Firebase
#3I use Hasura for this purpose. With some hooks, you can achive offline mode, too. You need a bit tricky hacks to use Hasura permission system the way you want, though.
Tell me more about this!
Re: A Graph-Based Firebase
#4I use Hasura for this purpose. With some hooks, you can achive offline mode, too. You need a bit tricky hacks to use Hasura permission system the way you want, though.
Hasura does not offer syncing.
Syncing is hard :)
Re: A Graph-Based Firebase
#5> These triples say that the Layer with id 1 has a fontSize 20 and backgroundColor blue. Since they are different rows, there’s no conflict.
This sounds a lot like Bigtable (https://cloud.google.com/bigtable), which also does last-write-wins conflict resolution layer. So this is adding a GraphQL + frontend layer to it?
Re: A Graph-Based Firebase
#6I use Hasura for this purpose. With some hooks, you can achive offline mode, too. You need a bit tricky hacks to use Hasura permission system the way you want, though.
Hasura does not offer syncing. Syncing is hard :)
Aha, yup. My way of offline, is just store all commands offline and sync the command only. Syncing the view is hard.
Re: A Graph-Based Firebase
#7Very interesting. I came to many similar conclusions completely independently, even attempted to build a typesafe in memory datalog in typescript.
I also came to the conclusion that just exposing datalog triples as a query language would never feel right and tried to expose a graphql like language that generated the datalog triples.
IMO react relay offers a great similar offering with their normalized cache. Relay has great DX too and can be totally type safe. To my knowledge datalog is way too dynamic for static analysis.
That being said, I would love to try Instant out. I'm really happy to see innovation in this area.
Re: A Graph-Based Firebase
#8Another project with similar goals in mind: https://paulbutler.org/2020/the-webassembly-app-gap/
Also backed by YC.
Re: A Graph-Based Firebase
#9Are transactions supported in that solution or in the mentioned Datalog related ecosystem? I have built my own similar reactive inmemory triple store with typescripts type safety, but then I realized I still need transactions which are a bit of a pain, because transactions are bundling the otherwise separete triplets, so the atomic, independent logic of triplets and related effects breaks a bit. (I am sure it's solvable.)
Re: A Graph-Based Firebase
#10Are transactions supported in that solution or in the mentioned Datalog related ecosystem? I have built my own similar reactive inmemory triple store with typescripts type safety, but then I realized I still need transactions which are a bit of a pain, because transactions are bundling the otherwise separete triplets, so the atomic, independent logic of triplets and related effects breaks a bit. (I am sure it's solva…
The example code uses a `transact` function. But it really depends on what you mean by “transaction”. We don’t use a triple store at Notion, but we do use an abstraction that ensures a collection of operations either all succeed or all fail. We don’t support “interactive” transaction, where you can read, modify, write as an atomic group. This just isn’t desirable in a multiplayer or offline system - in cases we need that kind of consistency we use a normal HTTP API which is online-only.