REST has been the longtime standard in APIs, but as applications evolve, GraphQL is quickly gaining popularity. We detail differences, strengths, and weaknesses.

Fauna

GraphQL and REST have their pros and cons. Depending on what you're building, one could be a better fit than the other. Let’s examine some of the core differences between Graphql and REST, and get some insight into when one should be used over the others.

GraphQL vs REST: What’s the difference?

Benefits of working with REST APIs .css-l70tfw{box-sizing:border-box;margin:0;min-width:0;display:-webkit-inline-box;display:-webkit-inline-flex;display:-ms-inline-flexbox;display:inline-flex;padding:0;opacity:0;-webkit-transition:all .2s;transition:all .2s;font-size:20px;pointer-events:none;margin-left:8px;}

my tl;dr:
REST’s limitations: can’t control how much data to fetch. often leads to over-fetching and under-fetching of data within one API calls.
GraphQL addresses the limitations of REST by fetching the exact data clients need, no more no less, using just one API call.

I tried GraphQl once and I found it very slow compared with rest api, I don’t know if it’s my fault or it’s how it works since it do a lot of work behind the scenes. I will try to dive into it more and make a real project with it.
Do you think Graphql is slower than rest api??

I expected GraphQL to be explained in this article, but sadly it only explains REST and covers so little of GraphQL

Good overview of compare/contrast of the two API architectures.