Developer, streamer, Microsoft MVP and Twitch dev contributer. I love to code and share the knowledge. Check me out at https://www.twitch.tv/talk2megooseman
Nice post! Doing GraphQL on Azure Functions is so simple with Apollo server. I would recommend it to anyone so they can play around with GQL and keep costs down while they learn and grow. I started my own little series covering the journey.
Hi, my name’s Aaron Powell and I’m a Cloud Advocate at Microsoft. My area of specialty is front-end web dev and .NET (especially F#), but I enjoy doing silly things with technology.
That is the way that I tend to go for it, but it does have the downside of cold start potentially impacting your GraphQL endpoint, which is why it's worth looking at App Service as well.
Developer, streamer, Microsoft MVP and Twitch dev contributer. I love to code and share the knowledge. Check me out at https://www.twitch.tv/talk2megooseman
Hi, my name’s Aaron Powell and I’m a Cloud Advocate at Microsoft. My area of specialty is front-end web dev and .NET (especially F#), but I enjoy doing silly things with technology.
Hi, my name’s Aaron Powell and I’m a Cloud Advocate at Microsoft. My area of specialty is front-end web dev and .NET (especially F#), but I enjoy doing silly things with technology.
The best way to have a server that provides Subscriptions is to implement it on App Service as Azure Functions doesn't provide a way in which you can connect to a WebSocket (given it's event driven, a persistent connection wouldn't fit the model).
Building out an basic GraphQL API works flawless on AzureFunctions, However we ran into while trying to use subscriptions. Have you got GraphQL subscriptions working while running Apollo Server on AzureFunctions (node.js) ?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nice post! Doing GraphQL on Azure Functions is so simple with Apollo server. I would recommend it to anyone so they can play around with GQL and keep costs down while they learn and grow. I started my own little series covering the journey.
That is the way that I tend to go for it, but it does have the downside of cold start potentially impacting your GraphQL endpoint, which is why it's worth looking at App Service as well.
Personally I did end up migrating to App Services, another reason to do so is "Subscription" types
I haven't played with subscriptions in GraphQL yet, but I've got some ideas on how to tackle it using SignalR
Can you point to any working sample on how to get subscriptions working on Apollo Server with Azure functions. ?
Conveniently I wrote a blog post about this today - dev.to/azure/graphql-on-azure-part...
The best way to have a server that provides Subscriptions is to implement it on App Service as Azure Functions doesn't provide a way in which you can connect to a WebSocket (given it's event driven, a persistent connection wouldn't fit the model).
Building out an basic GraphQL API works flawless on AzureFunctions, However we ran into while trying to use subscriptions. Have you got GraphQL subscriptions working while running Apollo Server on AzureFunctions (node.js) ?