4 ms·

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 maj

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 6y ago
Where did you get plans to remove subscriptions?
- speedgoose 6y 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 6y 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 6y ago
Apollo removing subscriptions? I don't understand, aren't those a core feature of GraphQL?
- speedgoose 6y 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 6y ago
Why is that?
- speedgoose 6y 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 6y 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

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 6y ago

Where did you get plans to remove subscriptions?

speedgoose 6y 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 6y 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 6y ago

Apollo removing subscriptions? I don't understand, aren't those a core feature of GraphQL?

speedgoose 6y 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 6y ago

Why is that?

speedgoose 6y 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 6y 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