Is this like minimongo from meteor but for postgres? #1006
-
|
Hi at all, nice work and thanks for open source at first. To identify correctly what electric does, it seems to me as if it was anounced like Meteors real time sync feature with DDL and minimongo years ago. Is that a correct interpretation? Second, while using Hasura is there anything in better for us when using electric? Thanks for help and feedback. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
The closest analogy from the Mongo world would be "Realm for Postgres". The key difference to realtime sync is the local-first architecture and offline support. If you dropped Hasura onto Postgres and used optimistic writes to get local-first with GraphQL, then the key difference is that we solve the concurrency issues and provide a conflict-free and rollback-free development model. So no rollback handlers and no distributed systems complexity leaking back into your app layer. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks James @thruflo Not sure if you know Meteorjs and minimongo, it had the same target and solution - local first. The technology behind surely is quite different and not comparable. For Hasura that means - no Hasura anymore, when we want to use local-first by electric and get the benefits out from that, right? |
Beta Was this translation helpful? Give feedback.
The closest analogy from the Mongo world would be "Realm for Postgres".
The key difference to realtime sync is the local-first architecture and offline support. If you dropped Hasura onto Postgres and used optimistic writes to get local-first with GraphQL, then the key difference is that we solve the concurrency issues and provide a conflict-free and rollback-free development model.
So no rollback handlers and no distributed systems complexity leaking back into your app layer.