What is REST?

[@mahrig1829]

KZbin Search results about Web Dev, programming language tutorials usually shows old outdated videos which is hard to understand rather videos like this one. Your videos deserves definetely more likes. I would like to thank you for your hard work and effort. Im subscribed and looking forward for your next videos. Thank you again!

[@WebDevSimplified]

Thank you for the kind words. I am really glad that you enjoyed my video. Part of the reason I started my channel was because of all the outdated content on KZbin.

[@Amberussianbeauty]

This is the most used/amazing channel I’ve ever encountered!

[@developedbyed]

great one! now I'm gonna go rest... hehehe ( I know it's not funny).

[@WebDevSimplified]

I could use a rest as well 😴

[@cristhiancantillo4922]

Two of my favorite channels here... Amazing : )

[@johnallen7812]

Hello you so mazing

[@juanmluces]

Your jokes are so bad that they become funny xD

[@moisessoto5061]

Fbi youre under a rest for that joke

[@playboy6622]

You are just amazing. We didnt have a teacher like you in our school. We all mugged the code up and couldnt reproduce it as we didnt understand the logic. By looking at all your videos, I can say I am gaining the confidence to build a website

[@javxa]

The simplest and clearest explanation of REST. Thanks a lot!

[@ShafiqNazrin]

This is probably the easiest way to explain REST. Definitely a genius to come up with this.

[@karaokewaala9107]

This was so simple, i was scratching my head reading all about it on the internet

[@jackfrost8969]

This guy is literally blessing🙏

[@iconicbehaviour]

It's been about 10 minutes since I first came to your channel and I am on my second video already! Great job and really loving it :)))

[@WebDevSimplified]

Thank you so much! I really hope you love the rest of my videos as well.

[@hashmatali4409]

i've been working on rest api for a year. But today i learnt what is REST. you simplify the complex things so beautifully.

[@WebDevSimplified]

Glad I could help

[@juvenalgonzalez5291]

I've read so many different explanations of REST and this is by far the clearest explanation. Thank You!

[@callmekaymusic]

iam a south african and this content is helping me in my computer science degree

[@WebDevSimplified]

I'm really glad I can help!

[@khandoor7228]

Hey WebDev this series looks really cool, I'm really looking forward to it. I subscribed a couple weeks ago because I thought you really knew your stuff so I'm excited to track this series. Let's go brother!

[@WebDevSimplified]

Thanks! I really hope that you enjoy the series and future videos to come.

[@Pareshbpatel]

Very clear and succinct introduction to RESTful APIs - Thank you, Kyle {2021-06-07}, {2021-09-08}

[@anthonytcool350]

Bro, this is a great. I can understand the difficulty and confusing of the REST in 3 mins. Keep doing your great work!

[@tfilipow7]

Thank you, no one has explained that to me in such an efficient way.

[@JM-tu8mg]

Great video! This is the best explanation of REST I have ever seen!

[@pavelvitov2773]

Great video man, helps a lot as I have an exam tomorrow. :D

[@GaborNeogrady]

Lovely tutorials, really simple. Greetings from Hungary :)

[@rociodesantiago867]

Thank you! That was such a simple and straight to the point explanation!

[@johongirrahimov2343]

I'm honored to learn from you. my sensei

[@davidr.flores2043]

Thank you my friend. I'm a beginner and your explanation was very clear. Best regards.

[@B.Aboobaker]

Thank you. Great explanation.

[@albertoazinar1209]

Found your channel today. I'm already learning alot. thankiu

[@nicolasesteban699]

Perfectly explained, thanks!

[@nwobodogeorge5370]

Thank you. The video is concise and straight to the point.

[@STRIPPEDSTAR]

Perfect, concise explaination!

[@pinkym6934]

FFFFAAAAAAAAAANNNNNNNNNNNNNNTTTTTTTTTTTTTTTASTIC!!!!Crystal clear and precise....:)))

[@Faxulous]

thank you. SIMPLE AND CLEAR! Great.

[@chickenjoy]

So in equivalent to SQL, is it: GET = Select * POST = Insert into PUT = Update DELETE = Delete

[@melzz]

Am i do this wrong? I only use get and post.... And even to retrieve data, sometime i use post.....eventhough it is using for create... Is it a bad practice?

[@Kessra]

In all honesty, this is NOT what REST is or should be. I understand that most people do think that this is REST, but no, this is definitely NOT what REST is. CRUD may be such a tiny portion of REST, which furthermore is just an oversimplification and circumsision of the actual HTTP operation definition. I.e. DELETE just removes the mapping of the URI to a resource but gives no promises or the like to a client that the resource is also removed. I.e. multiple URIs may be used to express the same state, which internally may point to the same database entry. On deleting one resource this would affect other resources as well as they litterally share the same data. Though RFC 7231 only states that the mapping of the URI to the resource is removed. Similar to resource creation which is not limited to POST only. Just read up in RFC 7231 on PUT what it should do when it created a resource. After all, its semantics are "replace the current state a resource has identified by a URI with the one provided in the received payload" and not simply update that resource. And if the server had no state for that resource yet, it will be created. HTTP at its heart is just a document management system and it's a side-effect of the document management we use to deduce some business logic of it. I'd recommend to search here on YT for a great talk Jim Webber held in 2011 talking about REST and DDD, or a talk given by Stefan Tilkov back in 2014 also on REST. Also, tooling such as Swagger or OpenAPI behave more like tradidional RPC IDLs, such as Corba, SOAP, Java's RMI, .NET COM+, ...) with further tooling that generate even stub-classes for such APIs. How much more does it take to realize that this is RPC through and through. Such things are tailor made for exactly that API and if the API ever introduces changes you have the same outcome as in traditional RPC environments. Further, often clients assume that resources represent a certain type and thus you will end up in typed resources (--> soabits.blogspot.com/2012/04/restful-resources-are-not-typed.html ) instead of relying on proper content-type negotiation or working on a "server teaches client what it needs to know to make furthre decisions/requests" principle.

[@ПанЧиЛо]

Thanks, Kyle. Your videos really helps me to understand different topics. Btw, don't you mind if I translate some of your videos to Russian?

[@genzee4567]

till date wondering what is REST AND REST API but u solved it. i have some doubt - how will server understand which request (GET/POST/DELETE/PUT) should be executed? Because the URLs r same

[@dubola5777]

Thanks. short and sweet!

[@I5starjordan]

Damn that was good and short

[@unknowned1113]

What's the point of the PUT and DELETE methods and routes if you can't even do the request using the standard HTML form?

[@sankharr]

Thanks for this video :)

[@inesborges4857]

but aren't rest apis noy supposedto be modified. they are only supposed to use the get method because you can only get the details to use in your own application?

[@pixel690]

is it bad that i have essentially been doing this all along by making web requests and even creating nodejs apis without understanding the meaning of REST

[@alejandropoirier6493]

is there a difference between RESTful and REST APIs?

[@stephenfoster9009]

I did not see a difference in the URLs for [ GET ] and [ POST]?

[@GAMINGWITHDESTRYER]

Sir, how the URL decide is this is a post req or a get req if the URL is same for both

[@alextheblockchaindev]

Great Explanation! Good Job!

[@WebDevSimplified]

Thanks!

[@RelaxingTomato]

Hey thanks a lot for this great explanation. Quick question: if I build a service that's sole purpose is to expose details about a specific ID using the rest format (i.e. GET /user/id) is this still considered a "REST API" or do I need to provide the full CRUD scope to be considered a REST API ? Hope this makes sense. Thanks

[@WebDevSimplified]

That would still be a REST API. As long as your API is built using resource routes and uses standard endpoints for CRUD then it is restful.

[@ctbram0627]

I don't understand the first two urls you show as [GET] and [POST] are exactly the same??? How are you determining one is a [GET] and the other is a [POST]?

[@rutger3188]

u define that within your call client, such as post man. Normally u use specific routes like GetUser and CreateUser to understand the difference in your code. But when making a request you define within your client if it is a post, get, patch or delete request ;)

[@BullishBuddy]

awesome! and subscribed

[@umaedu3097]

could someone help me understand how to make a three different page website according top this model? thank you :)

[@sagyblecher9258]

thanks kyle

[@KeshavKumar-re1ls]

Hey Kyle. I think you should use a mic closer to your mouth. because the sound in some of the videos sounds hollow and it echoes.

[@alibabarahaei2229]

Perfect❤

[@peppigue]

I use yt with chromecast a lot, and for some reason some vids are so choppy on the audio. Unfortunately I this is true for this and some other vids on this channel. Annoying, because this is a good source of the info I need...

[@dev-playing-gt]

I heard it's better just use method with the same urls than representing the types in urls. like DELETE method-/user/ (O) /user/delete/id (X) how do you think?

[@WebDevSimplified]

I agree. I think it is easier to work with, but some people prefer the other way. In 90% of APIs you will see it with the same URL and just the method changing.

[@dev-playing-gt]

Thank you for the quick and clear reply!

[@dj1805]

Greate, Thank you!!

[@chinmayghule8272]

There's no PATCH request in this video.

[@vaibhav_naik]

Well explained

[@smallzebra19]

Only 60k?

[@warren1192]

thank you!

[@shitheegg9563]

❤️

[@johnnyxp64]

unfortunately many if not 80% of the web devs don't use [put] or [delete] ... but instead they use [post] to achieve those results... 😒😒😒

[@WebDevSimplified]

That is very true. Hopefully videos like this will help new developers utilize all the HTTP actions.

[@andriibilych4983]

Not gonna lie, I understood that rest has something to do with urls, after that it's like white noise to me, thank you nevertheless

[@sunnyboss3103]

Sir what is restful web API ?? pls explain

[@WebDevSimplified]

A restful API is just an API that uses rest for its endpoints. Most APIs that you will see are restful.

[@sunnyboss3103]

@@WebDevSimplified thank you sir 🙏🙏 pls make more videos I watch every videos of yours channel and it's amazing job 💜

[@kylepaulmcfly]

Rest always been seems complicated to understand.

[@darkantoinevs]

Even though it is a good overview of HTTP APIs, this is not what REST is about. Roy Fielding himself mentioned that REST is not about CRUD : roy.gbiv.com/untangled/2009/it-is-okay-to-use-post . You do not mention the use of hypermedia to navigate through the API at all.

[@bryantgrimminger5481]

It's what you get when you sleep.

[@WebDevSimplified]

This is the true answer.

[@Ada-zg2qb]

🙏🙏🙏

[@gosnooky]

Updating a resource should use PATCH instead of PUT

[@Runnable19]

So it's basically CRUD

[@hanesmitter1469]

Patch for updating

[@code5829]

Recourses self taught backend engineers? Anyone reply to this

[@LLF1234]

Why they don't simply call it CRUD (Create, Read, Update and Delete) operations instead? So much easier to remember and it makes much more sense.

[@fraterrr6560]

Terrible…. I don’t learn anything, I watched this entire video and I still don’t know what REST is…….

[@neildutoit5177]

Jeez dude. This entire thing is wrong. Rest says nothing about http. http is one protocol that can be used to implement rest. Rest says nothing about CRUD. CRUD operations can be implemented over REST. So can other operations. The discussion of URLs is irrelevant because REST resources are identified by rels not URLS.. Most importantly, you say nothing about Hypermedia as the Engine of State Transfer, which is fundamental to REST. What you're describing here is a glorified RPC server. Not a REST endpoint.

[@splitlang]

Like 100 thank you

[@WebDevSimplified]

You're welcome!

[@himbary]

Why didn't u include patch?

[@SuperLukiano]

What the f...k? I didn't understand a thing. I use PHP and JS and all those methods mentioned above but I wanted to know the background of that fancy REST word and you haven't made it clear at all.

[@devidasa9637]

Uh...it could not have been clearer