These are quite a lot of questions, let me try to answer all of them
First of all, there seems to be some general confusion between server-side subscriptions, and client-side subscriptions.
Server-side subscriptions are webhooks that are triggered for a certain mutation. You can create such a server-side subscription by adding the necessary information in the
prisma.yml file, just like in the example you linked to. Here, you can add a webhook URL that will be called with a HTTP POST request, when the subscription is triggered. It’s up to you which language to use when implementing that endpoint, and whether that endpoint is a serverless function or an actual server.
Client-side subscriptions in Prisma are using the websocket protocol and therefore require a long-running connection between your client and your server.
The function component from the Graphcool Framework is not present in Prisma, but it should be fairly straightforward to use a tool like Serverless to setup a serverless function.
Which example are you referring to? If it’s this example, then this is about client-side subscriptions. Could you please provide a bug report here where you describe what doesn’t work in the example?
No, Graphcool Framework and Prisma are two separate tools. Please read this thread to understand the differences. Would love to discuss any further questions about this topic there as well
With all this being said, there seems to be a problem with setting up server-side subscriptions currently. This is being discussed in this issue. I just added a note with a workaround there as well.
Hope all of this makes more sense to you now. Please let me know if that’s not the case