Це відео не доступне.
Перепрошуємо.

REST vs GraphQL

Поділитися
Вставка
  • Опубліковано 19 кві 2024
  • 🚀 neetcode.io/ - A better way to prepare for Coding Interviews
    🧑‍💼 LinkedIn: / navdeep-singh-3aaa14161
    🐦 Twitter: / neetcode1
    ⭐ BLIND-75 PLAYLIST: • Two Sum - Leetcode 1 -...
    #neetcode #leetcode #python

КОМЕНТАРІ • 21

  • @bogdan206
    @bogdan206 3 місяці тому +75

    The most beautiful part of graphQl is that you don't have to use it

    • @softcoda
      @softcoda 3 місяці тому

      Why is this the most beautiful thing?

  • @Taurdil
    @Taurdil 3 місяці тому +5

    Literally confused REST with HTTP. REST is not about HTTP codes. Read damn paper.
    REST could be applied even to GraphQL if that makes sense for your use case. GRPC as well, although cacheability might be a problem

  • @muhammadkamilbinmohdfauzi6137
    @muhammadkamilbinmohdfauzi6137 3 місяці тому

    Great vid man, learned a lot from you

  • @RaijinTheGreat
    @RaijinTheGreat 3 місяці тому

    these are very helpful thank you

  • @ramsey2155
    @ramsey2155 3 місяці тому +1

    Or you just properly define an rpc on your api that returns exactly the infornation you need

  • @nlsnboa8187
    @nlsnboa8187 3 місяці тому +1

    Grpc?

  • @cdcm
    @cdcm 3 місяці тому +5

    isn't graphQL dead ?

    • @jerofff
      @jerofff 3 місяці тому

      definitely not

    • @conundrum2u
      @conundrum2u 2 місяці тому

      one would hope, but there's a lot of people out there who think because it was invented by someone at Facebook that it needs to be applied everywhere. it was invented to address Facebook's terrible architectures and people are using with greenfield projects. it's so dumb

  • @JTCF
    @JTCF 2 місяці тому +2

    Oh wow, using the actual http codes the way they are intended to be used! So innovative!
    The video is full of filler...

  • @cclementson1986
    @cclementson1986 3 місяці тому

    SOAP?

  • @yassinesafraoui
    @yassinesafraoui 3 місяці тому +1

    Why does it feel like he's slowed down

  • @aswinnath8580
    @aswinnath8580 3 місяці тому +1

    so graphQL is better right?

    • @natescode
      @natescode 3 місяці тому +11

      Nope, just a tool. It is better for certain use cases.

    • @aswinnath8580
      @aswinnath8580 3 місяці тому +1

      @@natescode thank you for info

    • @conundrum2u
      @conundrum2u 2 місяці тому

      in most cases, no. it's a bit of an antipattern.

  • @Simran_048
    @Simran_048 3 місяці тому

    don't get it
    but get the story behind

  • @conundrum2u
    @conundrum2u 2 місяці тому

    that's actually not specific to graphql. you're confusing traditional microservices with REST. You can define REST style endpoints that query a lot of data from micro or monolith services. this crosses over into CQRS territory. man, I would really recommend you learn more because your videos are misinforming newbies and that's harmful

    • @sophiophile
      @sophiophile 2 місяці тому

      It is not inherent, but it is typical of design patterns. Generally REST endpoints do one thing.

  • @gro967
    @gro967 3 місяці тому

    GraphQL replaced REST for anything API Gateway related.
    Good is has come to such a broad usage, it’s the best API pattern currently out there.