GraphQL Requests

What you’ll learn
  • how GraphQL HTTP requests are handled by the deployed cloud infrastructure and application code

Diagram

Webiny Cloud Infrastructure - API - GraphQL Requests
info

For brevity, the diagram doesn't include network-level cloud infrastructure resources, like region, VPC, availability zones, and so on. Check out the Default VPC and Custom VPC topics if you're interested in that aspect of the deployed cloud infrastructure.

Description

The diagram shows how HTTP requests (GraphQL queries and mutations) travel through the deployed cloud infrastructure. Request are primarily issued by the Admin Area, or Website applications, but of course, can be issued by other clients as well.

The steps are the following:

  1. The GraphQL HTTP request first reaches the Amazon CloudFront A.
  2. The request is forwarded to the Amazon API Gateway B.
  3. The Amazon API Gateway invokes the GraphQL Server Lambda function C.
  4. Depending on the issued GraphQL operation, the Lambda function's code may issue one or more requests to other cloud infrastructure resources:
    1. Amazon Cognito D to perform identity authentication
    2. Amazon DynamoDB E or Amazon ElasticSearch Service F to perform database queries
  5. Once the code execution has completed, an HTTP response is returned back to the Amazon API Gateway B.
  6. The Amazon API Gateway B forwards the request to the Amazon CloudFront A, which again forwards it back to the client.
Last updated on by Adrian Smijulj