Awesome. So in terms of design you have
src/graphql.ts handling the in-bound queries and passing them to the resolvers which run inside the same function. When using AWS Lambda, how do you think about running your graphql server inside one function versus calling a separate AWS function for each resolver?
I’m using Apex Up to deploy my graphql-yoga server to AWS Lambda. I think it has a reverse proxy but it’s basically the same thing as yours whereby my server is inside one function (plus playground). I’d love to figure out how to speed up cold starts. I’m transpling from Typescript. See this repo I put together up-graphql-yoga-server-example