What Is GraphQL? REST vs. GraphQL

Checkout our bestselling System Design Interview books:

ABOUT US:
Covering topics and trends in large-scale system design, from the authors of the best-selling System Design Interview series.

[dmitrylubyanov]

Probably the most easy to understand video I've seen about differences between REST and GraphQL. Thank you!

[youngKOkid]

GraphQL seems like an ambitious & interesting idea, as well as a horrendous footgun. Thanks for the wonderful explanation as always!

[casual_sky]

This is a fantastic video! Thanks for the comparisons, it really helped me understand what was going on. I was having trouble understanding the concepts seeing as not many people explain it this simply and I didn't have time to dig into the documentation... Thanks a lot. I'll be sharing this video for anybody else who needs a quick, no fuss intro to graphql.

[golden_smiles]

It is most quick, constructive and comprehensive essence of knowledge without any extra BS payload like memes and distracting videos. Thank you, sir.

[Necessaryy]

The graphics and animations are simply next level.

[MrPilz]

Great work as always ! I'm really impressed by the quality of your slides

[TwoWholeWorms]

Added this to our standard training tools. Brilliant job, looking forward to your future videos! ^^

[molomekeys]

the work on animation is incredible very inspiring

[RaymondPeckIII]

Interesting. I implemented some similar features in the H2O-3 REST API framework back in 2015. You can white- or black-list fields, and specify which if any child objects to return in the payload, so you didn't have to make many REST requests and assemble an object graph yourself inside the client. The query language was just REST with a couple optional parameters on top of it. It doesn't require a schema (it's schema-on read, with automatically-generated rich metadata for the schemas), or a special query language. You just specify the field paths for any child or grandchild classes you want returned.

The API is defined in a very lightweight way, simply by creating a parameterized class for each class in the API. No boilerplate, no IDL.

[SOMEONE-eqbu]

That was most well and detailed explanation I've seen

Liked and subscribed

[chamaraanu]

One of the best videos to grasp the idea of GraphQl.

[khalilshaik]

very clear explanation!
instantly subscribed!

[goldfishbrainjohn]

I like this channel.
Valuable technical system design series.

[juliahuanlingtong]

Great piece!
Would love to have a piece elaborate on the caching behaviors of HTTP GET leveraged by browser, CDN and servers mentioned in the video.

[zoomzoom]

thank you for this! extremally valuable resources, please keeping making this content

[nyplace]

amazing animations, a very clear explanation, thank you!

[matthiasdebernardini]

such a great video - love the channel!

[taunado]

Beautiful animations and explanation. Thanks.

[dushyantchaudhry]

2:11 to 2:21 a superb concise explanation of the difference.

[JuliLukiKon]

Thanks for the explanation!
That was very helpful!