Our GraphQL endpoint will be handled by a single AWS Lambda function, via either the GET or POST HTTP method. For completeness, the diagram of the AWS API Gateway request to the AWS Lambda function looks like the following:
While it may seem a bit pedantic to review this, I think it's important to stress the simplicity of this pattern and the advantages gained by adopting GraphQL. Of course, there are always trade-offs, and GraphQL is no different. Since so much functionality is pushed down into the logic layers, most of your time will likely be spent in application code, ensuring your API provides the same functionality as ...
