Your tutorials are amazing, and particularly for 2 reasons: 1. you get right into the info, and don't put fluff in the vids 2. your discussions are very clear and well organized Thanks!
I was going to said the same but some just did it lol Thank you for making this videos and sharing you have a lot of Really Good Content in Your TH-cam Channel. I Would love to see more videos from you in the future.
Thank you. You could also say that API is a counterpart of UI. While UI is for humans to interact with software, API is what allows software to communicate with another piece of software. UI has buttons, windows, mouse etc., API is a set of defined methods and parameters that one computer program can pass to a another piece of software, and as a response receive some data that it will then be able to use.
This amazing. I've gotten so sick of googling things like API and reading plain English things like, "API is a way to communicate between applications" or something too complicated to understand. This video is perfect for those who understand an intermediate amount of knowledge without industry experience.
I can't explain in words how perfect and layman your explanation was. I am so blessed to have people like you who are contributing to the IT community by sharing immense knowledge. I just typed what is API vs REST and youtube just blessed me with this video. Now I am so confident to explain about API and REST API if someone asked me to. Thank you and much respect. Planning to watch the entire web basics concept playlist of yours.
Best Rest explanation ever. I'm starting learning Java and its frameworks and there a lot of job announces requiring Rest. Still trying to learning more about webservices, SOAP x REST, XML x JSON, and so on. This video helps me a lot. The examples makes your videos very special! Keep doing. Many thanks.
an application programming interface (API) is an endpoint which encapsulates but exposes the state and functionality of an object, imagine it as a description written on the OUTSIDE of a closed door, which tells you what you can expect to find if you were to OPEN the door and look inside the room, but you are NOT supposed to open the door and look at the things INSIDE the room !! you are expected to "trust" that the description that is written for you on the OUTSIDE of this closed door tells you EVERYTHING you need to KNOW in order to make full USE of ALL the "hidden things/contents" that are wrapped/encapsulated INSIDE the room, you are expected to {be able to} use ALL the features of the room and its contents by just studying {looking at} the description that's written OUTSIDE of the closed door for example, if object1 has two fields field1_name; field2_age; and four methods (member functions) method1_assign_name() method2_assign_age() method3_get_name() method4_get_age() you can USE the state (change how it looks) of object1 as object1.field1_name = New_Value ; object1.field2_age = New_Value ; and the functionality (the things that object1 can do or that can be done with it) as object1.method1_assign_name( Argument_1, Argument_2, Argument_x ) ; object1.method2_assign_age( Argument_1 ) ; object1.method3_get_name() ; object1.method4_get_age() ; so all these six things above, when we combine them, we can list them as follows object1.field1_name object1.field2_age object1.method1_assign_name() object1.method2_assign_age() object1.method3_get_name() object1.method4_get_age() now this ^^ COMPLETE list of items (ALL the members of object1 which in fact are ALL the features of object1) that you see above "describes" the API of object1 in addition, for the functionality part of the API (the methods - the things that object1 can do or that can be done with object1), it is usually important to know what these methods RETURN (bring back) when you call/invoke them to make them PERFORM their intended work/action, so instead of describing the methods in a lazy way as shown above, a more proper way of describing the methods of an API is as follows : int object1.method1_assign_name() String object1.method2_assign_age() long object1.method3_get_name() Boolean object1.method4_get_age() so the proper/full API for object1 is now as shown below object1.field1_name object1.field2_age int object1.method1_assign_name() String object1.method2_assign_age() long object1.method3_get_name() Boolean object1.method4_get_age() and even the fields (which describe the state) of object1 should ideally be PROPERLY described in the API by showing what type of values (data types) they can accept, as follows String object1.field1_name int object1.field2_age so the FINAL/full proper API for object1 now is : String object1.field1_name int object1.field2_age int object1.method1_assign_name() String object1.method2_assign_age() long object1.method3_get_name() Boolean object1.method4_get_age() An API "library" on the other hand is a collection/group of APIs, whereby each single API in the library describes how you use the features of a single object {within that library}, such that with an API library of 35 objects, you will have 35 APIs for each object, whereby API number 18 within these 35 APIs describes how you use ALL the features of object18 as an encapsulated object since it (object18) exposes its state and functionality through the description written in its API, the API of object18 gives you a full description of "how to make use of" object18 Regards Tebogo M. Motlhale
thank you very much. This is great video, I tend to become bored and irritated with some videos that has too much fluff and when they over complicate tutorial by using big words, but yours is great and direct to the point.
First of all thank you so much for your effort to make all of your videos so informative and well structured yet possibly the most simple. I'm a medical doctor. But for the project that I'm working on, I really need to understand what these rest api, uri, resource, web etc. With the help of your video, I'm opening my eyes a little by little into the IT world. I will be very grateful if you can make a video generally about coding for non-experts like me. But I have to say that your videos are so simple that even ordinary people like me can digest the information on them. I may be asking too general or dumb question, because of my lack of knowledge about IT world. But even only a explanation of code structure, slash, coma, basic principles, basic programs, little bit of history, Everything will be highly appreciated. Thank you so much again and please keep up this good work.
I have a database for managing my hobby (my first database). I'm now building a web application as an interface to the database (my first web development). v1 of the web application works but it isn't pretty. My db tables are getting rather large/long. Now working on v2 and want to include "pagination". This let to Javascript's Fetch() API which lead to REST APIs and that to RESTful web services. SPAGEHETTI!!! I don't need someone to explain how to code an API, I need someone to explain the concepts. BUDDY, YOU NAILED IT! Halfway through your video I clicked SUBSCRIBE. Job well done. Now I'm off to learn the REST rules and will then will ensure my web application, which I admit is only for my own use, will be a RESTful web application.
"""Anything that lets software components talk and communicate with each other is API and API can be in anyform ; its implementation and what it consist doesn't matter""
This was the best explanation - thank you SO MUCH for including the client-side code. That's where I get confused and you made it so clear. Thank you!!
Thanks for the great videos! I was just looking for a simple HTTP explanation annd came across the first video on the playlist, and ended up watching the whole thing. Really helped me!
Amazing Explanation! This was properly paced and extremely Beginner friendly. Loved the OOP example that you used in the beginning. Usually people break these videos off into multiple videos, that leads to a lot of confusion and procrastination.... all the important basics in one video was really helpful!
Amazingly explained! Thank you very much for taking the time to explain this so beautifully, I subscribed, and intend to cover as much as possible from your channel. Your explanation flows straight to my brain, and ... Wow! I'm like super new into software, only know fundamentals of programing, and feel this is attracting my attention to what I would actually prefer to do in the context of CS. Again, thanks!
Great video, eager to keeo learning from your explanations. As a side note, for me, i would have preferred the topic of what it is first, before of, what felt to me, was taking the viewer through the mess of misconceptions first
Thanks for clearing up a few things. I’ve been using and making restful web services for a while now and always wondered if there were any differences between the terminologies expressed.
Great video, concise and to the point! I did not understand that much the code at 13:20, but it motivated me to get to know more about all this stuff anyway. Thank you a lot!
Thanks for your feedback, Steffano. That was just a super simple express(node library) api server. Just to demonstrate how REST APIs look like. Of course, things are more advanced for real world software.
5 ปีที่แล้ว +2
Hi, I liked your video very much because in fact it clarified some interesting details to me, such as how we should use verbs and data and why, but I noticed a couple of errors in the implementation you're using to demonstrate them, not horrible ones but they could be fixed so users can write the code from your video and make it work. The first one I spotted was a trivial one and it is the spelling of the url, it says seviceProviderApp.com instead of serviceProviderApp.com. I know that's not important for the example but detail are important to me. The second and most important one is that you're using "/user" for the uri on the server piece of code and "/api/user" on the client, so they can't communicate that way. That applies also to /user/add which is /api/user/add on the client side. I hope this helps I think your work is great by the way. Thanks for your work of putting this great information together.
One question: What if a developer doesn't follow the REST rules? What different will it really make on the implementation of an web application? Any thoughts?
I started with this video but I going to see all the series. Thanks. Maybe a video of what happens when you close or cancel in the browser the page? A question in one of my interviews. The language of the page affects? Thanks again.
Kudos from Poland for the awesome videos. I've been through most of them, and they are really helpful! Also, you sound very academic, which makes it even better :)
I'm a tech writer, what parts of the "what you should know" do you think you'd like for me to know if I needed to do API documentation? This is a great tutorial, btw
I have only watched it for 10mins and dude, I am impressed. I haven't read one article neither watched any other video which explains this topic the way you have explained in this video. You made it so simple to understand. Thank you my friend :). By the way, is that a Russian accent? I like that too.
Apt video about REST APIs What would have made more sense is to add imperatives / advantages of Why adopt the REST protocol But I give this a five star all the same!
I have just started my career and your videos are very helpful. Your videos help me to visualize how things work in background. More videos from your channel would be appreciated bro! Thanks alot.
Hi! Thanks so much for this video and it's pretty helpful! I have a question regarding the slice at 10:00 - may I ask why "GET" is "Not RESTful"? My understanding is "GET" is the correct method to get response in REST? Thank you and looking forward to your answers!
I believe you would have received your answer in 3 months. In case you haven;t - he didn't say GET is not RESTful. If you see the intent of that request, it is to delete a particular user. In first example, it is done by GET request and a much detailed URI. Instead it should have been via DELETE verb. The one reason you can think of developers doing is ease of use to do any operation via a single VERB/Method. Hope it is clear enough.
@@sawajaysharma Hi ajay, thanks so much for the response! Actually I haven't got my answer in the past 3 months and your response solves my problem! Really appreciate that.😁
I have a doubt: "REST" is the architectural style while "RESTful API" are typically web services implementing such an architecture. With "REST API" we refer to "RESTful API" or are they something different?
Thank you for watching! I hope you enjoyed the content! 😊 Support the Techcave to produce more content! ko-fi.com/thetechcave
I guess you are a Moroccan judging from the accent, I am really proud to see someone from my country posting this quality content, keep up.
Your tutorials are amazing, and particularly for 2 reasons:
1. you get right into the info, and don't put fluff in the vids
2. your discussions are very clear and well organized
Thanks!
I was going to said the same but some just did it lol Thank you for making this videos and sharing you have a lot of Really Good Content in Your TH-cam Channel. I Would love to see more videos from you in the future.
Thank you. You could also say that API is a counterpart of UI. While UI is for humans to interact with software, API is what allows software to communicate with another piece of software. UI has buttons, windows, mouse etc., API is a set of defined methods and parameters that one computer program can pass to a another piece of software, and as a response receive some data that it will then be able to use.
Wow.probabaly the best definiton of API
Nicely explained!
This amazing. I've gotten so sick of googling things like API and reading plain English things like, "API is a way to communicate between applications" or something too complicated to understand. This video is perfect for those who understand an intermediate amount of knowledge without industry experience.
5 years after. Still valuable thanks f the detailed explanation and seriousness in this tutorial.
I can't explain in words how perfect and layman your explanation was. I am so blessed to have people like you who are contributing to the IT community by sharing immense knowledge. I just typed what is API vs REST and youtube just blessed me with this video. Now I am so confident to explain about API and REST API if someone asked me to. Thank you and much respect. Planning to watch the entire web basics concept playlist of yours.
I appreciate your kind words! I'm really happy you find it helpful! 😄
This should be global definition of APIs and web services. Very well explained!
This is the best explanation of REST API I have seen so far in YT, thanks for sharing
Hands down this is the best content about the subject on TH-cam.
Best Rest explanation ever. I'm starting learning Java and its frameworks and there a lot of job announces requiring Rest. Still trying to learning more about webservices, SOAP x REST, XML x JSON, and so on. This video helps me a lot. The examples makes your videos very special! Keep doing. Many thanks.
This is one of the best explanations I've ever watched on TH-cam. It's clear, on point and organised.
Amazing explanation! So structured, clear and focused on the subject.
Thanks a million!
an application programming interface (API) is an endpoint which encapsulates but exposes the state and functionality of an object, imagine it as a description written on the OUTSIDE of a closed door, which tells you what you can expect to find if you were to OPEN the door and look inside the room, but you are NOT supposed to open the door and look at the things INSIDE the room !! you are expected to "trust" that the description that is written for you on the OUTSIDE of this closed door tells you EVERYTHING you need to KNOW in order to make full USE of ALL the "hidden things/contents" that are wrapped/encapsulated INSIDE the room, you are expected to {be able to} use ALL the features of the room and its contents by just studying {looking at} the description that's written OUTSIDE of the closed door
for example, if object1 has two fields
field1_name;
field2_age;
and four methods (member functions)
method1_assign_name()
method2_assign_age()
method3_get_name()
method4_get_age()
you can USE the state (change how it looks) of object1 as
object1.field1_name = New_Value ;
object1.field2_age = New_Value ;
and the functionality (the things that object1 can do or that can be done with it) as
object1.method1_assign_name( Argument_1, Argument_2, Argument_x ) ;
object1.method2_assign_age( Argument_1 ) ;
object1.method3_get_name() ;
object1.method4_get_age() ;
so all these six things above, when we combine them, we can list them as follows
object1.field1_name
object1.field2_age
object1.method1_assign_name()
object1.method2_assign_age()
object1.method3_get_name()
object1.method4_get_age()
now this ^^ COMPLETE list of items (ALL the members of object1 which in fact are ALL the features of object1) that you see above "describes" the API of object1
in addition, for the functionality part of the API (the methods - the things that object1 can do or that can be done with object1), it is usually important to know what these methods RETURN (bring back) when you call/invoke them to make them PERFORM their intended work/action, so instead of describing the methods in a lazy way as shown above, a more proper way of describing the methods of an API is as follows :
int object1.method1_assign_name()
String object1.method2_assign_age()
long object1.method3_get_name()
Boolean object1.method4_get_age()
so the proper/full API for object1 is now as shown below
object1.field1_name
object1.field2_age
int object1.method1_assign_name()
String object1.method2_assign_age()
long object1.method3_get_name()
Boolean object1.method4_get_age()
and even the fields (which describe the state) of object1 should ideally be PROPERLY described in the API by showing what type of values (data types) they can accept, as follows
String object1.field1_name
int object1.field2_age
so the FINAL/full proper API for object1 now is :
String object1.field1_name
int object1.field2_age
int object1.method1_assign_name()
String object1.method2_assign_age()
long object1.method3_get_name()
Boolean object1.method4_get_age()
An API "library" on the other hand is a collection/group of APIs, whereby each single API in the library describes how you use the features of a single object {within that library}, such that with an API library of 35 objects, you will have 35 APIs for each object, whereby API number 18 within these 35 APIs describes how you use ALL the features of object18 as an encapsulated object since it (object18) exposes its state and functionality through the description written in its API, the API of object18 gives you a full description of "how to make use of" object18
Regards
Tebogo M. Motlhale
Nice!
thank you very much. This is great video, I tend to become bored and irritated with some videos that has too much fluff and when they over complicate tutorial by using big words, but yours is great and direct to the point.
you are such a gifted provider of overview, simple & to-the-point explanations of unknown, complicated topics. Thank you
First of all thank you so much for your effort to make all of your videos so informative and well structured yet possibly the most simple. I'm a medical doctor. But for the project that I'm working on, I really need to understand what these rest api, uri, resource, web etc. With the help of your video, I'm opening my eyes a little by little into the IT world. I will be very grateful if you can make a video generally about coding for non-experts like me. But I have to say that your videos are so simple that even ordinary people like me can digest the information on them. I may be asking too general or dumb question, because of my lack of knowledge about IT world. But even only a explanation of code structure, slash, coma, basic principles, basic programs, little bit of history, Everything will be highly appreciated. Thank you so much again and please keep up this good work.
I have a database for managing my hobby (my first database). I'm now building a web application as an interface to the database (my first web development). v1 of the web application works but it isn't pretty. My db tables are getting rather large/long. Now working on v2 and want to include "pagination". This let to Javascript's Fetch() API which lead to REST APIs and that to RESTful web services. SPAGEHETTI!!! I don't need someone to explain how to code an API, I need someone to explain the concepts. BUDDY, YOU NAILED IT! Halfway through your video I clicked SUBSCRIBE. Job well done. Now I'm off to learn the REST rules and will then will ensure my web application, which I admit is only for my own use, will be a RESTful web application.
"""Anything that lets software components talk and communicate with each other is API and API can be in anyform ; its implementation and what it consist doesn't matter""
Finding this channel is like finding a diamond
Never had a better breakdown of REST and RESTful services than this... Nice work
It's 2021 and still, your's is the best explanation I found so, thank you for that!!
Thank you for your kind comment!
This was the best explanation - thank you SO MUCH for including the client-side code. That's where I get confused and you made it so clear. Thank you!!
This is the best explanation of the RESTful API that I have ever seen. Thanks :)
FINALLY someone who can put it simple and clear. Thank you!
The best explanation of REST API on YT till now !!
Really helpful for beginners to learn about API & REST api,..even non developer can understand your explanation,..simple and on point!!Great Work!!
Amazing, after this explanation I feel confident enough to start digging deeper into the topic. Thanks
very informative with sample applications and illustrations. Thank you and we look forward to more of your work. You've got a new subscriber! :)
Excellent overview! Short, concise, and easy to understand. I look forward to reading your dissertation. Thank you for sharing
Your tutorials are the best I have ever seen! Easy to understand and best of all you show some javascript code at the end
Thanks for the great videos! I was just looking for a simple HTTP explanation annd came across the first video on the playlist, and ended up watching the whole thing. Really helped me!
Kudos to the one who made this video. It's very easy to understand. I have subscribed to your channel. Thank you so much for sharing.
The best video on REST by far.
this is the best explanation that I could find! thank you sir.
Amazing Explanation! This was properly paced and extremely Beginner friendly.
Loved the OOP example that you used in the beginning.
Usually people break these videos off into multiple videos, that leads to a lot of confusion and procrastination.... all the important basics in one video was really helpful!
one of the best explanation of REST. Loved it. Thanks for sharing.
FInally a really clear and on point explanation. Thank you for uploading this!
Amazingly explained!
Thank you very much for taking the time to explain this so beautifully, I subscribed, and intend to cover as much as possible from your channel.
Your explanation flows straight to my brain, and ... Wow!
I'm like super new into software, only know fundamentals of programing, and feel this is attracting my attention to what I would actually prefer to do in the context of CS.
Again, thanks!
best video among all the videos present here on TH-cam. great!
Great video, eager to keeo learning from your explanations.
As a side note, for me, i would have preferred the topic of what it is first, before of, what felt to me, was taking the viewer through the mess of misconceptions first
Thanks for clearing up a few things. I’ve been using and making restful web services for a while now and always wondered if there were any differences between the terminologies expressed.
This is so on point! You present the content in a clear and easy comprehensible way! Really great work!
Amazing!
clear ,easy and direct explanation
Great video, concise and to the point! I did not understand that much the code at 13:20, but it motivated me to get to know more about all this stuff anyway. Thank you a lot!
Thanks for your feedback, Steffano. That was just a super simple express(node library) api server. Just to demonstrate how REST APIs look like. Of course, things are more advanced for real world software.
Hi, I liked your video very much because in fact it clarified some interesting details to me, such as how we should use verbs and data and why, but I noticed a couple of errors in the implementation you're using to demonstrate them, not horrible ones but they could be fixed so users can write the code from your video and make it work.
The first one I spotted was a trivial one and it is the spelling of the url, it says seviceProviderApp.com instead of serviceProviderApp.com. I know that's not important for the example but detail are important to me.
The second and most important one is that you're using "/user" for the uri on the server piece of code and "/api/user" on the client, so they can't communicate that way. That applies also to /user/add which is /api/user/add on the client side.
I hope this helps
I think your work is great by the way.
Thanks for your work of putting this great information together.
Thank you very much for your videos, they all are really very good! From Argentina 🇦🇷
One question: What if a developer doesn't follow the REST rules? What different will it really make on the implementation of an web application? Any thoughts?
short and detailed information, well done
I started with this video but I going to see all the series. Thanks. Maybe a video of what happens when you close or cancel in the browser the page? A question in one of my interviews. The language of the page affects? Thanks again.
Thanks. A great lesson. It is important to have key terms both defined and explained.
Best explanation ever! Thank you!!!
Kudos from Poland for the awesome videos. I've been through most of them, and they are really helpful! Also, you sound very academic, which makes it even better :)
Good introduction to the REST API world. Thanks so much for putting it in :)
I'm a tech writer, what parts of the "what you should know" do you think you'd like for me to know if I needed to do API documentation? This is a great tutorial, btw
Thank you very much. You have cleared my biggest doubt: "Why to use different methods if I can perform anything using one method like get or post?"
Exactly - but now we know it complies with REST standards using the appropriate meaningful HTTP verbs
That was such a great explanation! Thank you :)
You are amazing!! Please make a video on 'REST vs SOAP'. Thank you!! And all the Best!!!🎈
Nice! - very succinct, keep up the good work!
I have only watched it for 10mins and dude, I am impressed. I haven't read one article neither watched any other video which explains this topic the way you have explained in this video. You made it so simple to understand. Thank you my friend :). By the way, is that a Russian accent? I like that too.
Do you have an video on the advanced topic of stateless communication?
mate, love your explanation vids! Just the clean style I was looking for.
I love your explanation! Much respect...
Good explanation REST App thank you
I like the ecplanatiin and fact you talk fast, which is not boring.. l bet you are moroccan :)
very good presentation, well explained.keep going broooo
Thanks for this class.
This was great! thank you so much!
Very good explanation, thanks a lot.
Thanks for demystifying...would love to see more!
Very good explaination....Thanks :-)
Excellent presentation!
nice and simply stated. thanks for this
Well explained. Thanks man.
Thank you so much. Would love to see more videos from you
Your videos are amazing , Thank you ♥
Great explanation ! Thank you
Thanks alot for this amazing session.
Could you give a presentation for python implementation of API?
Great overview!
But, after explaining, early on, that using additional verbs in the URL is redundant, you use 'add' in the example: POST /users/add :(
Apt video about REST APIs
What would have made more sense is to add imperatives / advantages of Why adopt the REST protocol
But I give this a five star all the same!
Nice work, upgrade my school courses.
tbarkellah 3lik khoya
Great presentation. Thank you.
This is a great explanation 👏
Great material!
Very nice videos, pls make more videos on web
Great Explanation
Best explanation
Can someone explain me how you can use REST(exactly the GET protocol of HTTP) in a secure way ? I mean GET can be logged by any web browser
thank you .... great job!
I have just started my career and your videos are very helpful. Your videos help me to visualize how things work in background. More videos from your channel would be appreciated bro! Thanks alot.
Hi! Thanks so much for this video and it's pretty helpful! I have a question regarding the slice at 10:00 - may I ask why "GET" is "Not RESTful"? My understanding is "GET" is the correct method to get response in REST? Thank you and looking forward to your answers!
I believe you would have received your answer in 3 months. In case you haven;t - he didn't say GET is not RESTful. If you see the intent of that request, it is to delete a particular user. In first example, it is done by GET request and a much detailed URI. Instead it should have been via DELETE verb. The one reason you can think of developers doing is ease of use to do any operation via a single VERB/Method. Hope it is clear enough.
@@sawajaysharma Hi ajay, thanks so much for the response! Actually I haven't got my answer in the past 3 months and your response solves my problem! Really appreciate that.😁
Thank you very much for the clear explanation of the subject and I hope you success in the coming videos
Great very easy to understant trainng!
♥️🔥
very well made video
you're amazing keep going broo
Hi, first of all Thanks !!! Is Source Code available at 13:21 of the Tutorial?
Thanks !!!
Very Nice!!
I have a doubt: "REST" is the architectural style while "RESTful API" are typically web services implementing such an architecture. With "REST API" we refer to "RESTful API" or are they something different?
It's the same actually 🙂
You definitely “NOT” disappointed me👌👌👌👏👏👏