Це відео не доступне.
Перепрошуємо.
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
The most beautiful part of graphQl is that you don't have to use it
Why is this the most beautiful thing?
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
Great vid man, learned a lot from you
these are very helpful thank you
Or you just properly define an rpc on your api that returns exactly the infornation you need
Grpc?
isn't graphQL dead ?
definitely not
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
Oh wow, using the actual http codes the way they are intended to be used! So innovative!
The video is full of filler...
SOAP?
Why does it feel like he's slowed down
so graphQL is better right?
Nope, just a tool. It is better for certain use cases.
@@natescode thank you for info
in most cases, no. it's a bit of an antipattern.
don't get it
but get the story behind
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
It is not inherent, but it is typical of design patterns. Generally REST endpoints do one thing.
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.