-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Subscriptions #191
Comments
Originally posted by @manonthemat in #179 (comment) |
Originally posted by @AdrienLemaire in #179 (comment) |
Hey guys. Is there any work on this issue? still waiting for subscriptions. I hope this feature will be next. |
Hey, we are not actively working on this. We have had some internal discussions though, we realise that to get a scalable solution would be a lot of work - something to look into after we are finished working on 2.0.0(relationship properties and cursor based pagination). |
I see. Thank you Daniel for the response and good luck with your work. |
+1! Love this repo and the people working on it, I think that this project has so much potential. I see you've had some internal discussions on this feature, and now that both relationship properties and cursor based pagination is implemented I just had a couple of quick notes on scalability & functionality for this feature:
Example use cases for OGM subscription functionality:
Of course, this has other implications, such as if the application is scaled to more than one instance, how do we prevent these events from happening more than once if each instance is performing the same functionality? That might be something that we can just leave to the user to figure out (bull queue comes to mind as a solution) as it seems outside of the scope of this application. However, for ease of use, it might be nice to also send an "event id" for each event to make it easier to schedule jobs in bull queue. Other ways this functionality could be implemented:
I am really looking forward to this feature! Let me know if any help is needed with this. Thanks! |
HI @AdrienLemaire I apologise for not answering earlier. I will close this issue now, further development in this area will be covered by separate issue |
Is your feature request related to a problem? Please describe.
Looking for the ability to subscribe to events via the Neo4j GraphQL API.
Additional context
Came from here #179
The text was updated successfully, but these errors were encountered: