It's time to explore together the wonderful world of GraphQL and REST. Let's take a look at what GraphQL is, what REST is, and when you should choose one over the other.
What is the need they exist to serve?
Why and how to use them?
And we'll see the four advantages GraphQL has over the REST-full style of APIs.
And then the 2 major disadvantages that you have to watch out for if you use or create an API in GraphQL.
But before that, let's start at the beginning:
What is GraphQL?
GraphQL is a way to create web APIs. I've already made a video talking about APIs in general, and REST web APIs in particular.
REST is the standard way to organise an API. But GraphQL is challenging that position of dominance.
To understand GraphQL, and to understand why it exists, I will be comparing it with the way REST APIs are organised. Because GraphQL is in part a response to the problems that REST has.
