What Is GraphQL? REST vs. GraphQL

Sdílet
Vložit
  • čas přidán 8. 11. 2022
  • To get better at system design, subscribe to our weekly newsletter: bit.ly/3tfAlYD
    Checkout our bestselling System Design Interview books:
    Volume 1: amzn.to/3Ou7gkd
    Volume 2: amzn.to/3HqGozy
    ABOUT US:
    Covering topics and trends in large-scale system design, from the authors of the best-selling System Design Interview series.

Komentáře • 198

  • @dmitrylubyanov7277
    @dmitrylubyanov7277 Před rokem +178

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

  • @youngKOkid1
    @youngKOkid1 Před rokem +76

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

  • @Necessaryy
    @Necessaryy Před rokem +12

    The graphics and animations are simply next level.

  • @golden_smiles
    @golden_smiles Před 9 měsíci +6

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

  • @MrPilz28
    @MrPilz28 Před rokem +3

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

  • @casual_sky2
    @casual_sky2 Před rokem

    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.

  • @molomekeys3938
    @molomekeys3938 Před rokem +4

    the work on animation is incredible very inspiring

  • @ramkanagu
    @ramkanagu Před 11 měsíci +16

    Nicely explained! In ten years down the line, GraphQL will be identified as an anti-pattern in the industry. Though it may seem very easy and attractive initially, it would become more complex once the schemas become big. REST is simple and easy to implement. The only caveat with REST is multiple api calls to backend. The better and a traditional approach should be by introducing orchestration services for any frontend that requires more complex data models from the back end.

    • @GameboyZoneRocks
      @GameboyZoneRocks Před 5 měsíci +1

      Can you give an example of orchestration services for frontend which will circumvent GraphQL? Your comment was interesting for me.

  • @SOMEONE-eq5bu
    @SOMEONE-eq5bu Před rokem

    That was most well and detailed explanation I've seen
    Liked and subscribed

  • @TwoWholeWorms
    @TwoWholeWorms Před rokem +1

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

  • @chamaraanu
    @chamaraanu Před rokem

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

  • @goldfishbrainjohn2462
    @goldfishbrainjohn2462 Před rokem +2

    I like this channel.
    Valuable technical system design series.

  • @khalilshaik6161
    @khalilshaik6161 Před rokem +2

    very clear explanation!
    instantly subscribed!

  • @RaymondPeckIII
    @RaymondPeckIII Před rokem +4

    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.

  • @zoomzoom1889
    @zoomzoom1889 Před rokem +1

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

  • @jamesT008
    @jamesT008 Před rokem +2

    To the point and precise explanation. Nothing bla bla !!
    Very nice!

    • @drift_ah1518
      @drift_ah1518 Před rokem

      exactly what i thought - nice to spend exactly the minutes required to appraise oneself of a technology. plus i especially liked his no nonsense take on the pros and cons. a really good job/video

  • @nyplace1
    @nyplace1 Před rokem

    amazing animations, a very clear explanation, thank you!

  • @SinnuC
    @SinnuC Před 5 měsíci

    Complete brief video, thank you!

  • @taunado
    @taunado Před rokem

    Beautiful animations and explanation. Thanks.

  • @juliahuanlingtong6757
    @juliahuanlingtong6757 Před rokem +5

    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.

  • @matthiasdebernardini3388

    such a great video - love the channel!

  • @belhamyou2766
    @belhamyou2766 Před 8 měsíci

    Fantastic video, clear and short

  • @jacquesmatike9289
    @jacquesmatike9289 Před rokem +2

    Good explanations ... good animations !!

  • @dushyantchaudhry4654
    @dushyantchaudhry4654 Před 4 měsíci

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

  • @charuwaka1
    @charuwaka1 Před rokem +2

    The way you explained is TOP NOTCH

  • @JuliLukiKon
    @JuliLukiKon Před rokem

    Thanks for the explanation!
    That was very helpful!

  • @usamesavas9848
    @usamesavas9848 Před rokem

    Wow, very concise. Thanks for the video.

  • @PlectrumShorts
    @PlectrumShorts Před 7 měsíci

    Terrific overview and I *really* appreciate the caveats!

  • @deepanshukacher1536
    @deepanshukacher1536 Před rokem

    Really clarify my understanding of their usage

  • @vskovzgird
    @vskovzgird Před rokem +1

    Dude, you are the best. Thanks! Keep it up!

  • @dhirajnavale3861
    @dhirajnavale3861 Před rokem +3

    Finally this video has come 🥳🥳🥳, was waiting for so long. Thank you ❤️❤️❤️

  • @eminberkay
    @eminberkay Před rokem

    Excellent explanation, thanks! subscribed 👍

  • @jashgopani32
    @jashgopani32 Před rokem +1

    Amazing video, animatin and presentation!

  • @aminaomar9173
    @aminaomar9173 Před rokem

    Thank you for this great explanation.

  • @angelsancheese
    @angelsancheese Před rokem

    Thank you for the video! I learned something new

  • @cold_2477
    @cold_2477 Před rokem

    What a beautiful and informative video.

  • @whereispie
    @whereispie Před rokem

    Nice and stylish tutorial, thanks

  • @mineralisk
    @mineralisk Před rokem +1

    Thanks for the quality content.

  • @HaroonCodes-fj8mp
    @HaroonCodes-fj8mp Před 11 dny

    Very Well explained.

  • @sscapture
    @sscapture Před 2 měsíci

    Love your videos! Thank you so much!! ❤

  • @julivanespi
    @julivanespi Před rokem

    great video. easy to understand

  • @ernestoginotome2453
    @ernestoginotome2453 Před 4 měsíci

    Thank you very much for the explanation.

  • @pandyaakash5647
    @pandyaakash5647 Před měsícem

    Great Job buddy. Impressed

  • @andriikozakevych5669
    @andriikozakevych5669 Před rokem

    Great explanation! Clear and easy.
    Thanks a lot!

  • @dadno_sound4533
    @dadno_sound4533 Před rokem

    Learned a lot here!

  • @tiagosutter8821
    @tiagosutter8821 Před rokem +3

    thanks for content! suggestion: Odata, or maybe a video about "Rest vs. Odata vs. GraphQL"

  • @mohamedk.badenjki8781
    @mohamedk.badenjki8781 Před rokem +2

    Thank you for the great video. What tool / software are you using for the video animation?

  • @salamander1782
    @salamander1782 Před rokem

    Your videos are a god send

  • @userss9096
    @userss9096 Před rokem

    Great explanation!

  • @RafaelCorreaGomes
    @RafaelCorreaGomes Před rokem

    Amazing, thank you for sharing it!

  • @Ricardo-fg1bc
    @Ricardo-fg1bc Před rokem

    your videos are pretty good!! thx

  • @alexandervashchuk7795
    @alexandervashchuk7795 Před 3 měsíci

    great breakdown, thanks

  • @user-rv1bx8hx4v
    @user-rv1bx8hx4v Před 6 měsíci

    Thank you! Great video.

  • @user-qy7mb5ho9e
    @user-qy7mb5ho9e Před rokem +1

    Fantastic Motion animation btw

  • @eXit-mm3zg
    @eXit-mm3zg Před rokem

    Love your videos!

  • @manu144x
    @manu144x Před rokem +14

    It always seemed to me that graphQL is only worth it beyond a certain level of complexity and when you're dealing with an extremely varied array of clients each needing different fields, different data, different implementations. This gives the clients maximum flexibility and you move a lot of the complexity to the client side. If you don't want to implement hundreds of endpoints and API's you just create the graphql middleware, schemas and you're good to go.
    But security is a big risk, you need to make sure sensible data is not being returned in any way, not to mention you introduce a lot more possibilities for bugs.

    • @tomu5642514
      @tomu5642514 Před 11 měsíci +2

      Exactly, for me it's pretty clear that the main use case of graphql it's one where you have as you said a varied array of clients who evolve independently from your api implementation and you have a complex data model that otherwise requires multiple endpoint implementations. Only in this case the tradeoff between this extra layer of complexity and cost it's worth for a business.

  • @TheRedbeardster
    @TheRedbeardster Před rokem +1

    Nice one, thanks!

  • @user-qy7mb5ho9e
    @user-qy7mb5ho9e Před rokem +1

    Thx! So helpful!!

  • @victormanuelfrancodev

    Nice explain! thanks

  • @doronsvable
    @doronsvable Před rokem

    Thanks Great Explentation

  • @mitotv6376
    @mitotv6376 Před rokem +1

    Nice explanation

  • @eltreum1
    @eltreum1 Před 11 měsíci +8

    GraphQL was designed by Facebook to solve over fetching problems aggregating data lakes containing overlapping/duplicate data sometimes from uncontrolled 3rd parties for a global service that processes millions of write and read queries per hour 24/7. It can be useful for taming bloated data lakes or getting more out of old systems. If you are building a new system ground up you probably won't need it unless your data models are very complex with giant records, but probably a just bad design.
    I have seen startups fail because they wasted time and money on GQL when they didn't really need it or the complexity it adds made getting the service to work well difficult or fragile. Don't engineer like FB and Google until you are that big and make a system that gets the objective work done well and code it so it can grow and modularize later if needed.

  • @swdRanaP
    @swdRanaP Před rokem +2

    which software you use to crate this kind of animation video? please tell me. and thank you so much for shareing this wonderful explanation.

  • @yp5387
    @yp5387 Před rokem +133

    In my company we use GraphQL as primary API and it is not good. We are planning to move everything to REST api. Knowledge gap is the biggest trade off for us. New talent is having hard time wrapping their head around GraphQL queries. REST is pretty simple and easy to understand thus less development time for all the developers.

    • @alexkey9372
      @alexkey9372 Před rokem +20

      same here. biggest mistake we've ever done. REST API is way more mature. when graphql reaches that point then we might re-consider.

    • @TheVasx
      @TheVasx Před rokem +18

      Might be a bit of devs fault. New hire or not, graphql for FE is something you learn in a couple of days if you have some experience

    • @alexkey9372
      @alexkey9372 Před rokem +11

      @@TheVasx in our case, it wasn't the knowledge gap but the performance. all graphql requests are POST, therefore is really hard to cache them. We thought for bigger project would be better, but that was proven to be a naive thought.

    • @TheVasx
      @TheVasx Před rokem +11

      @@alexkey9372 oh yea, if you depend on caching its all a big clusterfuck 🔥🔥

    • @yp5387
      @yp5387 Před rokem

      @@TheVasx Agree. And sooner or later, caching will come into the picture for sure.

  • @mokyyds
    @mokyyds Před rokem +1

    Like, your video content is very professional, what software did you use to make the video? thanks

  • @allezvenga7617
    @allezvenga7617 Před rokem +1

    Thanks for your sharing

  • @michaelcharlesthearchangel

    Nice comparison!

  • @dungnguyenanh1085
    @dungnguyenanh1085 Před rokem

    Great video!

  • @code-tips
    @code-tips Před rokem +1

    Nice video 👏👏. Which tool are you using for making such great videos?

  • @romulosendoromulo
    @romulosendoromulo Před rokem

    Very nice, thanks!

  •  Před rokem +27

    Great video!
    But sincerely I would continue to use JSONAPI instead of GraphQL.
    JSONAPI is super nice, supported by a lot of frameworks and it's build around the specific fields to be fetched just when they are needed... not to mention the pre-build filters that you can specific on your resources and simplify the way you filter for particular records and collections

    • @sadashivshinde9150
      @sadashivshinde9150 Před rokem +5

      Thats the biased devloper inside u

    •  Před rokem +1

      @@sadashivshinde9150 Maybe 😂

    • @orion.5611
      @orion.5611 Před rokem

      which good resources are available for learning JSONAPI. i have found a small number and i dont understand it fully

  • @sourabhjana1278
    @sourabhjana1278 Před 9 měsíci

    cool explaination

  • @YusanTRusli
    @YusanTRusli Před rokem

    great video!

  • @vlog.444
    @vlog.444 Před rokem

    Super explanation

  • @thanhsonha7009
    @thanhsonha7009 Před rokem

    Great Video.

  • @starkest
    @starkest Před rokem +2

    great explanation, as usual

  • @rahatsshowcase8614
    @rahatsshowcase8614 Před rokem

    this was best ! because everyone was speaking regarding graphql directly and i was thinking its a sql languange XD

  • @edwardokech4347
    @edwardokech4347 Před rokem +21

    Awesome video...receiving all resources from one request seems great for GraphQL. However, not sure about its security capabilities and the fact caching is a headache. As a lead Engineer, I'll recommend GraphQL for our internal tools still not convinced about using it in our production apps.

    • @M3t4lstorm
      @M3t4lstorm Před rokem +7

      How would GQL differ from a security perspecific than any other HTTP based API...

    • @semosancus5506
      @semosancus5506 Před rokem +6

      @@M3t4lstorm Makes you wonder about the Lead Engineer....

    • @vitorguidorizzzi7538
      @vitorguidorizzzi7538 Před rokem +3

      @@M3t4lstorm Not really a security issue per se, but graphql makes it easier to write very expensive queries, rest can rely on basic rate limiting but graphql also needs to block clients spaming tremendously expensive requests

  • @thanhauco
    @thanhauco Před rokem

    Thank you for great video, tRPC is now gaining growth and replace graphql

  • @virtuoso_hub
    @virtuoso_hub Před 9 měsíci

    great! how do you prepare your presentations? so beautiful!

  • @whonayem01
    @whonayem01 Před rokem +1

    Thanks

  • @shutanovac
    @shutanovac Před rokem +5

    Frankly I didn't understand the part with the table scan that could bring the DB down. Someone care to elaborate please?

    • @YBuda101
      @YBuda101 Před rokem

      I'm not sure what the details are of his example, but as presented, that risk is possible with REST calls too. Unsure why he singled it out as a GraphQL problem

    • @DF-ss5ep
      @DF-ss5ep Před rokem +1

      For example "find a user whose name matches a regex", and the name column in the DB has no index. In practice, I don't think such a query is likely to bring down the entire service, although it's possible. It would depend on how many of these queries are executed. In a bad scenario, all other queries become slow because the DB is overloaded, which causes more and more requests to accumulate, until everything fails. I don't know how GraphQL works, but with simple REST + SQL, you would use the circuit breaker pattern and use a "bouncer" (a proxy) in front of the db

  • @DF-ss5ep
    @DF-ss5ep Před rokem +40

    To be fair, you can also accidentally do a full scan of a table in SQL too. Maybe it's just a bit less likely because developers who build the queries are more aware of what's in it than frontend developers

    • @yannistheodorakopoulos5916
      @yannistheodorakopoulos5916 Před rokem +13

      Totally agree on that. But the main misconception with GraphQL is the following:
      Maybe this is the biggest mistake in GraphQL implementations. While it is meant to be a form of contract between the client and the server, in which the backend side plays the role of the aggregator that fetches data from different sources, people use it to communicate with the database layer instead.

    • @kimovitch7
      @kimovitch7 Před 5 měsíci

      @@yannistheodorakopoulos5916 I thought it was obvious that graphql should be used as a backend for frontend more than for data access layer, guess people relying on it to do stuff it's not that good for...
      Graphql should just stay away from your domain/business layer

  • @ReflectionOcean
    @ReflectionOcean Před rokem +1

    Rest: simple to implement and use, with inefficiency in specific occasions because of multiple API calls required
    GraphQL: flexible and efficient to use, but complex to implement and use and often relies on extra tools

  • @Vedarta
    @Vedarta Před rokem +2

    Great video, but I don’t see the advantage of GraphQL over JSONAPI. Also, there are several open source implementationsfor JSONAPI.
    I would only maybe use GraphQL to describe relations not predicted by a JSONAPI REST API, if that much.

  • @zaxx7884
    @zaxx7884 Před rokem +1

    GraphQL is great, but I'm a little worried about the delay when I put NodeJS as BFF in between. How do you all solution?

  • @nickolaskraus
    @nickolaskraus Před rokem

    I liked the nod to the SpaceX Dragon capsule in the GraphQL schema 😏

  • @Lost1nTranslation
    @Lost1nTranslation Před rokem

    Nice video

  • @chackokabraham738
    @chackokabraham738 Před rokem +1

    Hey alex, good Video, how ever i have two questions
    1. Is Odata and graphql sort of the same I mean you can fetch by the query or am I right in saying that the schema of odata is different and way different than Odata ??
    2. Do we need a specific type of database like a nosql or graph db for querying such information ??

  • @MythicEcho
    @MythicEcho Před rokem

    I immediately went to your channel to watch more videos, but the count is very low. But thats the catch, quantity > quality.

  • @wild_shaman
    @wild_shaman Před rokem

    GraphQL is a marketing tool. It requires way more server work to be done for really rare usecase. Usually it's better to use json rpc with predefined request differs.

  • @caro.girlwithflowers
    @caro.girlwithflowers Před rokem

    good job bro :D

  • @HANNAHSdigitaldiaries
    @HANNAHSdigitaldiaries Před rokem +1

    Is it same persistent tables for GraphQL and REST? If so, can GraphQL guarantee atomic operations across tables?

    • @vitorguidorizzzi7538
      @vitorguidorizzzi7538 Před rokem

      graphql is just a specification for http requests, it does not interfere with your tables.

  • @user-ib1pl5wg5w
    @user-ib1pl5wg5w Před rokem

    Where are they better to use in terms of safety and cost?

  • @MarcoLenzo
    @MarcoLenzo Před rokem

    Which program do you use for animations?

  • @satish1012
    @satish1012 Před 3 měsíci

    any one understood at 4:21 . What he meant? How does the entire table span occurs?

  • @marvhan888
    @marvhan888 Před rokem +1

    5 star video

  • @roman3249
    @roman3249 Před rokem

    In previous video I just watched they told that n+1 problem is a problem of GraphQL approach, in this video they told that n+1 problem is a problem of REST approach 🤯

  • @ahmedeox
    @ahmedeox Před 5 měsíci

    how is this in principle different from soap and exchangign wsdl schemas?

  • @neildutoit5177
    @neildutoit5177 Před rokem +1

    What is the GraphQL analogue for HATEOAS? I.e. how do you discover resources?