When you need to build an API, your mind will likely jump to REST, the de factostandard for API creation. However, this is about to change with GraphQL, as its popularity quickly rises.
Not everyone fully understands yet what GraphQL is all about, or why it's being declared as the successor of REST, and that's exactly what I'll clear up in this article. Here I'll show off GraphQL's main features and the advantages that it has over REST, highlighting a few points in which both differ.
The goal is to provide a brief explanation to anyone who still hasn't got to know GraphQL, and clarify exactly what it does better than REST, for those who are still skeptic about this technology.
Let's start with the very basics.