Learn AWS Serverless Computing

Core concepts

GraphQL is not a database, nor a library. Simply put, it is a runtime combined with a language for querying and accessing the backend data. We use it mostly to implement experience layer APIs where the response can match only the data that is needed by the client. It's really good when you need the data to drive the user interface, like when you have a data structure that multiple users are making changes to and you need to make updates to the view in real time.

The client sends queries that are evaluated against a predefined schema, which is a type system created and designed by ourselves. This defines what is possible for users to query, similar to an interface specification. It's here where you define all of the fields and ...