REST vs GraphQL | When to choose one over other | Tech Primers

[@TechPrimers]

⏱Chapter Timestamps ==================== 0:00 - Intro 0:23 - Agenda 1:16 - Differences between REST and GraphQL 1:44 - Practical example of GraphqQL 5:07 - Practical example of REST 6:20 - HTTP Methods 8:16 - Overfetching/Underfetching 9:57 - When to use GraphQL 11:54 - Usecase - Messaging Application 14:54 - Usecase - Ticket Booking Application 18:31 - Summary

[@franklinrowan5845]

I know im randomly asking but does any of you know a method to log back into an instagram account?? I was dumb forgot my account password. I would love any tricks you can give me!

[@adrianandres4928]

@Franklin Rowan instablaster :)

[@franklinrowan5845]

@Adrian Andres thanks for your reply. I found the site on google and im in the hacking process atm. Seems to take a while so I will reply here later with my results.

[@franklinrowan5845]

@Adrian Andres It worked and I finally got access to my account again. I'm so happy! Thank you so much, you really help me out :D

[@adrianandres4928]

@Franklin Rowan Happy to help :D

[@muks]

Very Interesting and useful. To summarize, can we safely say: GraphQL should be used when 1. We need to provide the client with minimal data, 2. Has need to know basis data requirement 3. Multi tenant clients 4. More front end centric apps like for e.g. mobile apps Rest should be used when 1. It can co exist with GraphQL but mainly to be used for stronger backend services, 2. No restriction in terms data flow and loading/unloading, 3. Multi http protocol support is required, 4. Huge no of backend services present in system design which needs to communication with each other, Please suggest, As usual Thanks for your efforts,

[@TechPrimers]

Perfect. Thanks for summarizing Mukul. I’m going to pin this comment

[@abhiroy82]

​@@TechPrimers , for overfetching problem, we can use RestTemplates for REST API to fetch required data instead of loading all data

[@geekthegeek730]

Man! you simplifies everything. Thank you for the video

[@animeshvaibhav5392]

Best explanation

[@AR-scorp]

Very good video. To the point. Great work.

[@TechPrimers]

Glad it was helpful!

[@rajganguly503]

Great video. very easy to understand. The use cases really make the difference. Thanks for the effort

[@jayaramuduc9030]

Thanks for Video, its useful to understand when to use Rest or Graphql

[@virtexamit]

GraphQL is handy way of reducing data over internet when clients interested in few fields. In past developer used json in built feature like serialize except these list of fields. For parsing query input RSQL, JAX-RS search.

[@user-mf8hf4uk3h]

Great explanation.Thank you!

[@SiddharthKulkarniN]

Super simple. Well explained. Kudos

[@DheerajKhatriatgoogle]

Small correction: to create the country(resource), convention is to use POST (not PUT) and to update the existing country(resource) we can use PUT. I guess by mistake these got swapped in your explanation.

[@RajaPandianCRP]

Thanks for a wonderful video yet again. This helped me look at your earlier video on Spring Boot and GraphQL and gain some knowledge on it.

[@dhanvihamsi]

Awesome video. Very informative

[@akshaykumar-bh4pr]

Great explanation 🔥👏🏻🙏🏼❤️

[@interviewin3steps709]

Explained very well

[@parvkapadia4217]

Interesting information about REST and GraphQl. Thanks

[@TechPrimers]

Glad it was helpful!

[@prabhakarmishra2182]

Really nice explanation

[@saikun0293]

Beautifully explained!

[@singh.karanbir]

Thanks for the video

[@mayankverma2818]

Too good

[@mediacmid]

Thank you for your effort. Could you please explain API vs Webhook?

[@tarankaranth8782]

excellent video, very clear. few questions 1. is there a client on top of http client 2. isnt it better to just use gql as it can do what a rest could provide as well the benefits of gql, using both can be a overhead, 3. is there a different frame work for getting the backend to use gql . 4. how would the specification look like in case of gql

[@RakeshM4u]

Well explained 👍

[@JaNaMSoNi]

Once again something useful and different 😊

[@rathnakumar731]

Awesome presentation 🙂

[@yogeshpatil-vx2pi]

Great explanation as always ..😊 If u can make Video on Kafka Confluent and IBM MQ .. would be a great help ...Thanks for ur sharings 🙏🏻🙏🏻🤟🏻🤟🏻

[@katienoland7390]

so helpful!

[@TechPrimers]

Glad it was helpful!

[@asgharhussain257]

Thanks for the comparison ,great video!! Are you going to implement those use cases demo in the upcoming videos?

[@TechPrimers]

I have already implemented them and explained them long back Asghar :). Check the description, I have linked those videos for reference.

[@asgharhussain257]

I will check thanks :)

[@varunram5413]

Great explanation. 👌

[@TechPrimers]

Glad it was helpful!

[@vizubhatt7556]

I have a usecase where I need to get data from database (around 12 queries to be executed with complex joins and multiple tables) and this data need to be served into a dashboard. Each query result need to be displayed into the dashboard. What can be the best approach here. A single Graph QL API or multiple Rest endpoints. I need to save database calls by caching as well.

[@HimanshuShrivansh]

How will GraphQL facilitates for multiple versions of API for mobile apps ? How can you support multiple schemas for different version of apps at same time ?

[@TechPrimers]

As a best practice, GraphQL goes against the versioning for API because it controls the schema inside the API, so you can add a different nested schema for that API and make it behave like a versions schema

[@MrSuryaKranthi]

Have doubt! Cant we acheive graphql capability thru a req body with post verb in rest style ?

[@TechPrimers]

Yes you can. Infant GraphQL is a better REST. Facebook created graphql due to overfetching of data in mobile devices and had to standardise their APIs across mobile and web

[@pradeepsubramani2641]

Very useful!! Just a small question please, do you think that there could be specific limitations on the info consumed via GraphQL?

[@TechPrimers]

Yes. GraphQL solves a specific problem which is over fetching and under fetching. Also the request payload is specific to a schema and a format which is specific to GraphQL specification. In REST, most of the time, there are no request payloads while querying data. Even if it has, it will be in json or parameters

[@pradeepsubramani2641]

Tech Primers Cool, Thanks!

[@kanishmalviya]

[GET] Rest API with payload would looks similar to GraphQL ?

[@krishkir]

From this video I understood that graphql is ideally fit for BFF (back end for front end design Pattern). Is my understanding correct?

[@TechPrimers]

Yes. let’s also take the example of Github. They expose GraphQL APIs so that developers can create any kind of application or cli over GitHub APIs. The developers can choose what data they need based on the graph based schema definition by GitHub

[@glimpsee7941]

I have been using GQL for about 8 months. UI loves GQL. Because you only get what you ask for the payload is very efficient. You remove all ambiguity from POST/GET requests. And you can combine multiple requests into 1 http request, so you dont need to chain http calls to load data

[@dhruva1221]

@@glimpsee7941 nice to know! Since I lacked knowledge around what ecosystem GQL requires, I was still thinking if leveraged the tuned architectural design for REST APIs, there may not have any under/over fetch results. But your experience around - combine multiple requests into 1 http request, show cases GQL is quite versatile. Thank you!!

[@JaNaMSoNi]

Hey bro, any example for Spring boot batch processing with resttemplate.

[@srilankaboys9416]

Good job

[@jagadeshdevarajan9662]

Interesting!

[@bobweee888]

I love you!

[@vishnumv5]

Thanks for the video.. What tools are you using for these drawings?

[@TechPrimers]

Just the basics Vishnu - Google Slides

[@anilkumargidijala9136]

How to find API's Prefect Suitable for Client Requirement

[@vardhamankothari3450]

Reminds me of elasticsearch queries

[@TechPrimers]

Nested n nested 😀

[@madhukargovind]

Rest is Archiectural Style vs GraphQL borh are represent the Data. As Java prespectve we use RestAPI to expose defferent type of media formats.But GraphQL does not. Thanks.

[@TechPrimers]

What unsupported media type are you specially looking for? Since both use HTTP they both use media types

[@oyrup]

Thanks, what's the best step to learn GraphQL

[@TechPrimers]

Trying hands on is the best option. Check my spring boot video on graphql, that’s a great start. Check the description for those links

[@slshani674]

Supper

[@dhiliph98]

Is file upload possible in GraphQL?

[@TechPrimers]

Yes Dhilip. Since GraphQL also follows HTTP protocol, you can leverage multipart content type to upload files like we do with REST

[@dhiliph98]

@@TechPrimers Cool.. I agree on your point that GraphQL is not a complete replacement for REST. No other video made this point clear. Thanks for the video :)

[@TechPrimers]

Cheers

[@softashutube]

Good explanation even though it seems very fast ...

[@TechPrimers]

You can slow down the video anytime by 0.5x or 0.75x :)

[@softashutube]

@@TechPrimers :) do i share my resume ? Ability to work on Java and GraphQL

[@TechPrimers]

I also work in a company buddy. TechPrimers is a hobby 🤓

[@YoEnigma]

Your intro video remind me something #MKBHD?

[@TechPrimers]

Dude his videos are insanely awesome and of great quality. Mine is nothing.