Replies: 2 comments
-
It would not help just getting changes as there is no way we can match queries against the changes etc. Also as it would pipe huge amounts of change data to GraphJin instances it would be very hard to scale and keep GraphJin performant. Our live query (subscriptions) implementation is lite, fast and very flexible even if you have hundreds of GraphJin instances it would scale nicely. |
Beta Was this translation helpful? Give feedback.
0 replies
-
thanks @dosco |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Would having a change steam from cockroach be a good thing ?
You would no longer be polling from graphjin but instead being fed the changes from the db .
there is golang code to do the same thing for other databases in the Wal-g project .
there might be other good aspects to this that I am not aware of I suspect
Beta Was this translation helpful? Give feedback.
All reactions