Welcome to this article!
Now that you know what GraphQL is, its history and how it works, it's time to understand it better.
If you haven't read the first article in the series, you can take a look at it afterwards because it has a very important content in case you want to understand better about the emergence of GraphQL and its operation.
I hope you have a wonderful reading.
As mentioned in the previous article, GraphQL is a declarative query language, this means that it allows you to query exactly and exclusively the data needed without worrying about how get for them. (It probably may not be very clear now, but I will discuss this point later :)).
GraphQL is actually a specification!
A specification refers to the description of characteristics of a language. The advantage of a specification is that it offers a common vocabulary and good practices for using the language.
GraphQL is a language specification for client-server communication.
A GraphQL query is hierarchical. Fields are nested within other fields and the query is shaped like the data that it returns.
GraphQL is driven by the data needs of the client and the language and runtime that support the client.
A GraphQL server is backed by the GraphQL type system. In the schema, each data point has a specific type against which it will be validated.
A GraphQL server provides the capabilities that the clients are allowed to consume.
The GraphQL language is able to query the GraphQL server’s type system.
In the next article, you'll see GraphQL in practice, the famous queries and how to do them. For this I will use a public API where we will make our queries.
If you have any questions, suggestions or comments regarding the content covered in this article, leave it in the comments!
If you liked the article don't forget to leave your LIKE ❤!