12 ms·

So basically Apollo GraphQL server could use the same mechanism for enabling GraphQL subscriptions right? Any idea what they currently use?

by raarts 5y ago

endisneigh 5y ago
GraphQL severs handle subscriptions websockets as well usually.
speedgoose 5y ago
They use websockets and a set of plug-ins to support redis, rabbitmq, or many other things. However, Apollo is planning to remove subscriptions for the next major release.
- ex3ndr 5y ago
  Where did you get plans to remove subscriptions?
  - speedgoose 5y ago
    In their roadmap here : https://github.com/apollographql/apollo-server/issues/2360#issuecomment-803149134 https://github.com/apollographql/apollo-server/issues/2360#i...
    - ex3ndr 5y ago
      That's completely different answer: They remove old graphql-subscirption-ws package that is not maintained anymore and split everything to separate packages to make them work faster. No one is going to remove subscriptions.
- raarts 5y ago
  Apollo removing subscriptions? I don't understand, aren't those a core feature of GraphQL?
  - speedgoose 5y ago
    > As far as subscriptions itself goes, Apollo Server 2 has a superficial integration with subscriptions-transport-ws that doesn't tie in to the plugin system, federation, Studio reporting, etc. And subscriptions-transport-ws isn't even the best maintained package that solves this problem. So 3.0 will remove that integration. I do hope that we do the work to add subscription support to the Apollo server-side platform as a whole sometime soon, but I can't promise a timeline for that https://github.com/apollographql/apollo-server/issues/2360#issuecomment-803149134 https://github.com/apollographql/apollo-server/issues/2360#i...
- arthurcolle 5y ago
  Why is that?
  - speedgoose 5y ago
    > As far as subscriptions itself goes, Apollo Server 2 has a superficial integration with subscriptions-transport-ws that doesn't tie in to the plugin system, federation, Studio reporting, etc. And subscriptions-transport-ws isn't even the best maintained package that solves this problem. So 3.0 will remove that integration. I do hope that we do the work to add subscription support to the Apollo server-side platform as a whole sometime soon, but I can't promise a timeline for that https://github.com/apollographql/apollo-server/issues/2360#issuecomment-803149134 https://github.com/apollographql/apollo-server/issues/2360#i...
    - arthurcolle 5y ago
      explanation makes sense, I didn't get the right interpretation from the initial comment - I guess there is just technical debt they are dealing with. They aren't trying to delete the feature itself, just roll it into their abstractions

So basically Apollo GraphQL server could use the same mechanism for enabling GraphQL subscriptions right? Any idea what they currently use?

by raarts 5y ago

So basically Apollo GraphQL server could use the same mechanism for enabling GraphQL subscriptions right? Any idea what they currently use?

endisneigh 5y ago

GraphQL severs handle subscriptions websockets as well usually.

speedgoose 5y ago

They use websockets and a set of plug-ins to support redis, rabbitmq, or many other things. However, Apollo is planning to remove subscriptions for the next major release.

ex3ndr 5y ago
Where did you get plans to remove subscriptions?
- speedgoose 5y ago
  In their roadmap here : https://github.com/apollographql/apollo-server/issues/2360#issuecomment-803149134 https://github.com/apollographql/apollo-server/issues/2360#i...
  - ex3ndr 5y ago
    That's completely different answer: They remove old graphql-subscirption-ws package that is not maintained anymore and split everything to separate packages to make them work faster. No one is going to remove subscriptions.
raarts 5y ago
Apollo removing subscriptions? I don't understand, aren't those a core feature of GraphQL?
- speedgoose 5y ago
  > As far as subscriptions itself goes, Apollo Server 2 has a superficial integration with subscriptions-transport-ws that doesn't tie in to the plugin system, federation, Studio reporting, etc. And subscriptions-transport-ws isn't even the best maintained package that solves this problem. So 3.0 will remove that integration. I do hope that we do the work to add subscription support to the Apollo server-side platform as a whole sometime soon, but I can't promise a timeline for that https://github.com/apollographql/apollo-server/issues/2360#issuecomment-803149134 https://github.com/apollographql/apollo-server/issues/2360#i...
arthurcolle 5y ago
Why is that?
- speedgoose 5y ago
  > As far as subscriptions itself goes, Apollo Server 2 has a superficial integration with subscriptions-transport-ws that doesn't tie in to the plugin system, federation, Studio reporting, etc. And subscriptions-transport-ws isn't even the best maintained package that solves this problem. So 3.0 will remove that integration. I do hope that we do the work to add subscription support to the Apollo server-side platform as a whole sometime soon, but I can't promise a timeline for that https://github.com/apollographql/apollo-server/issues/2360#issuecomment-803149134 https://github.com/apollographql/apollo-server/issues/2360#i...
  - arthurcolle 5y ago
    explanation makes sense, I didn't get the right interpretation from the initial comment - I guess there is just technical debt they are dealing with. They aren't trying to delete the feature itself, just roll it into their abstractions