Too Long; Didn't Read
In <a href="https://hackernoon.com/dive-into-graphql-part-i-whats-wrong-with-rest-709ebcb898dc" target="_blank">the first post</a> of the <a href="https://marmelab.com/blog/2017/09/03/dive-into-graphql.html" target="_blank">Dive Into GraphQL Series</a>, I’ve explained why REST isn’t such a good fit for today’s web and mobile applications. REST makes applications slow, harder and more expensive to develop, and too limited in functionality. We need a new hero, an architecture that allows to: