support subscriptions on remote schemas

hasura / graphql-engine

Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.

https://hasura.io

Apache License 2.0

31.03k stars 2.76k forks source link

support subscriptions on remote schemas #1599

Open dsandip opened 5 years ago

EddieVallejos commented 4 years ago

edilbertloquine commented 4 years ago

dasimandl commented 4 years ago

@ecthiender looking forward to this enhancement. What is the updated timeline for the release of this feature?

Tbaut commented 4 years ago

we're very much looking forward this feature, once the (remote schema feature is in). Having an easy setup for a subscriptions server it the essence or Hasura, remote schemas should follow this as well :rocket:

MaxmaxmaximusGitHub commented 4 years ago

I completely agree, we have a need for these architectures, and now we can not implement them through one endpoint

lostb1t commented 4 years ago

ironsalsa commented 4 years ago

+1 This would be a killer feature on top of the already killer Subscriptions feature! Even if it's similar to the poll-every-second way that it works for Postgres data.

joni7777 commented 4 years ago

+1 really need this feature 👍

jflambert commented 3 years ago

+1 would love remote subscriptions

naderfares commented 3 years ago

This is the only feature we are waiting to adopt Hasura.

chazmuzz commented 2 years ago

This is a real pain point for us right now

BenediktMiller commented 2 years ago

Support for this would be great!

L-U-C-K-Y commented 2 years ago

Is there any update on this part, something that you would consider in the near future?

cristianounix commented 1 year ago

rahulagarwal13 commented 1 year ago

Thank you for the request and comments for this feature. We would like to inform you that this is on our roadmap but we do not have a timeline at present. Please continue to follow this Github issue. We plan to publish on this issue a detailed RFC that covers all use cases and limitations of the feature. We welcome more detailed feedback from you once we provide those details.

For now it would be useful to understand more about your application/API design that requires you to use a remote schema subscription. Also we recently launched streaming subscriptions along with already supported functionality of live queries. We would be interested to know if your remote schema use-case is more streaming or live-query related?

jflambert commented 1 year ago

we use streaming and regular subscriptions equally, depending if our dataset is timeseries or a dimension respectively.

having said that, since this issue has been open for a long time, we converted all our remote schema queries to native postgres data sources.

our real killer need now is to allow subscriptions on remote relationships.