Why should I learn GraphQL?
Obviously, you should use the right tool for the job, right? … but often, what was the “right” tool, becomes the inferior tool, and frequently you don’t even notice…
The most popular way of talking to servers today, is using REST. REST offers a nice, easy to understand way of interacting with other servers, but think about this: Rest was introduced about 2 decades ago& That’s a long time in our world!
Let me ask you a question: how much has software development changed in 2 decades? Heck, how much has software development changed in 2 years? A LOT!
So, I think it’s fair to ask the question:
Do REST api’s still make sense, considering how we write software today?
To answer this question, let’s look at some of the problems with REST API’s:
Problem –> Many Concurrent Requests
Most non–trivial applications, make many concurrent REST api calls, before the app can even render a view& Why is this a problem? It might not be a problem, if the app has an excellent network connection (like our dev machines do), but it can be a horrible problem, on mobile devices with weak connections.
When mobile devices make many concurrent network requests, the response is often very slow, and the app might seem unresponsive… and it may not work at all. This can result in a dismal user experience.
Courses : 2