Hi @notsaved executeOperation:
Hi! We’re actually reworking the whole API right now as part of Apollo Server 4, which you can follow along on the version-4 branch or the milestone or the roadmap .
As part of this we’re getting rid of the old standalone functions like runHttpQuery which date back to Apollo Server 1 when there wasn’t even an ApolloServer object at all. ApolloServer should end up with two main entry points: one which is “execute this HTTP request” and one which is “execute this parsed operation”. The latter wi…
Thank you for your awesome product! We are really enjoying it a lot!
We have a particular production use case that forces us to run some logic after Apollo returns a response, but before the response is sent to the client. My question is can executeOperation be used reliably in production to achieve the is, although it shows only as a testing tool in your docs?
Are there limitations? caveats, pitfalls I need to be aware of?
Thanks in advance!
Hi @eric-naguras .
We are successfully using the executeOperation approach, which works great.
Currently, we have our project running on Heroku.
The plan is to move some of it to Cloudflare, and we even did a POC.
But please notice that the Cloudflare workers runtime is not a true Node.js environment , and thus many packages will not be able to run there. The error messages are also not always super helpful when building - but now you are warned
Based on these threads I don’t think there are any red flags that should stop you from using executeOperation in production. Maybe @glasser or @trevor.scheer might have some additional thoughts?
welcome to the forum! I found a couple posts that might help set some context for