An SDK is just a pre-packages set of code (for a specific language) that you don’t have to write yourself. Sometimes free and sometimes you have to,purchase them. In the case of this video, he is suggesting a “API-Interaction” SDK a developer would use. There are all sorts of other SDK’s out there including things like an SDK to simplify building a User Interface.
What you describe sounds more like a framework to me. Isn't an sdk (software development kit) something you use during the development rather than during actual runtime? Like a debugger etc. If I'm wrong (which is totally possible), could you tell me where you would draw the line between framework and sdk?
Prior to 2000 and there is a period of overlap, API was synonymous with function calls to external libraries exposed by other modules. It could be local, in memory, inter-process or remote libraries (or set of libraries SDK), whether it was binary or textual. API's around 2000 became synonymous with HTTP SOAP Web Services, and circa 2012 became synonymous with REST Web Services.
I'm glad to see this comment cuz what's being discussed in the video is a Web API instead of a regular API. Nobody I work with seems to understand there's a difference there.
Summary : - API : enables a system to communicate with another (without having to understand the complexity of the other system) - SDK : enables you to use APIs easily
@@bibekanandabhattacharjee952 My understanding is that sdk make it easier and faster to implement the api communication rather than writing code from scratch as it contains already all the methods needed to make api calls so we can just call the methods instead of writing the entire implementation. (Without reinventing the wheel)
I do not understand why some people put a thumb down ?? This video is design to give an overview of technical concepts. It does an excellent job and reach it goal, it simplifies those technical notions without giving wrong info.
API is also the library of interfaces to a desktop application or program. For example, you can integrate a program to Excel by using its COM API Interface. API is basic, it's only an interface. An SDK is more complete as it can have library API interfaces AND Tools to work with a specific technology. For example, if you want to develop mobile apps from Windows, you will need an SDK for a mobile OS, which is a complete set of tools to compile the code to Native Mobile OS, a debugger, an IDE, etc. etc.
When developing software, if you opt to create an SDK initially, design it in a way that allows for its use across multiple applications. An SDK is essentially a language-specific wrapper for APIs, so building distinct SDKs for similar applications is simply redundant. Additionally, remember that APIs are not constrained by language. Thank you.
Without SDKs we would need to send API requests using low level HTTP commands in whatever language we use. For example: Wanna talk to the Stripe API to get customer info using PHP? Without an SDK you probably need Guzzle HTTP library to send several requests to the /customer/ endpoints while needing to pass authentication credentials each and every time in your code. With their PHP SDK you aunthenticate once within your scripts and use the Customer object to get customer related data. SDKs facilitate using an API but are not the API and are not guaranteed be offered by the service/company that published the API. On the other hand, consuming the API using lower level commands offers us more control depending on how deep the SDK was implemented or not. I highly recommend checking out Stripe’s APIs and SDK documentation to get a good example of amazing implementation.
That's the idea. It should always be the guiding principles of good software. It's also great that the api or design when they are easy for the layperson to dive into the subject. Yes there is still a learning curve. If you look at search engines you dont ever had to think about issues about ranking or api or syntaxes almost never. Similarly, difficult concepts should be enjoyed by everyone. So there is a lot of work still. Glad you're enjoying it
I understand now what all this means, but sometimes you are just looking for simple definitions: API is a URL that does something (retrieve info, change something or perform an action). SDK is a file or files which have libraries that developers download and use in their proyects. Then it comes everything else that you brilliantly explained.
I save you some time here: API is if you make the requests yiursefl to an url to get, post, put etc. json data. SDK is a sort of module written by the service provider which contains functions you can use to complete your task. Example would be: upload_image("cat.png")
The down side of the SDK is its size. It has many funcrionality that one app might not use, also as SDK should be consistent over time, it should have the older versions which make them even larger over time. Also, as they run on our thread, they could have security issues, as well as malwares. It is better to make a good document for API vs an SDK. But big companies like to creare SDK to abscure data from developer. So never use an SDK unless it is open source.
Dear IBM Cloud, you disturbed me with your creative board and the talented trainer. Due to the amazement, I could not concentrate on what he is teaching. You innovated a little more than what you need to.
The advantage of SDK is just to avoid handeling api requests and response , but in reality SDK will not reduce the extra code form application . In simple word SDK is a sinthetic sugar over API
The main difficulties of existing API multilevel systems are: 1.The difficulty of porting a program code from one API interface to another. 2.Loss of functionality upon jumping from lower layer to higher.
Great video, I think this helps remind us of what an API ‘actually’ is…I personally tend to use the term API when I should really be saying ‘SDK’. I think another important concept to mention is that an API requires the logic to be hosted on 3rd party hardware, whereas SDK entails assemblies that you absorb as local references to your project and publish along with your build.
Very nice video... The one I was looking for... This is the kind of demo I or I think common folks like me, look for when dealing with these software abbreviations littering the entire cloud development ecosystem. Keep posting great videos like these.
You're definitely right. Sdk is made of api. Sdk leverage boilerplate, help you code with less effort. Sdk is a toolbox with screws, driver, humer. Api is what was used to make the toolbox and tools. Rest-Api est a tool made by Apis.
Sorry, but there seems to be some confusion here... An sdk is typically a KIT for fx DirectX and the likes. Its purpose to give you a toolset on the box. It's also often including tools for advanced debugging like the Windows SDK. You work with a specific product to create something on that platform. Api is an interface where for you ask a system or part of a system through a defined protocol to do some task for you. Api exposes something through a specific paradigm whereas SDK's contains more than just a facade. That's more like lego. REST is really a bad example, if we're being academic here. Cause we're talking about a very old paradigme that has been popularized. So, when people talk about Apis today, we tend to think HTTP, and not the likes of a C header file. It's a matter of level of technology Oh on a side note: I find it weird that this videos discusses a topic with no reference to C or C++ where these terms came to life and back in the hayday set many standards including this topic.
These is a crestal clear example. I really appreciate your effort and method of education. great thank you as I wish to see more and more of this videos.
The term API has been in use since the 1980s. Then it referred to callable functions to allow programmers to interact with the program product such as IBM CICS. In the 1990s we started to use the term with intra company systems. The customer information system at the bank where I worked had no screens of its own. Every action was performed by API calls. It is wrong to say that API calls are standardised, The same API could be called using XML (SOAP when it became popular bespoke initially) over HTTP or MQ or natively from a message switch. There is no requirement to use JSON or XML. It appears that the term API has been hijacked to mean REST, but that is only one implementation
They're both in the name. API, Application Programming...Interface - a way of programming an application. An application is already built and is already running. An SDK, Software Development...Kit. A set of tools (a kit) to develop software. This is independent from the application (a prebuilt binary). It's tools that you use to build a binary that does a specific thing. They usually consist if multiple APIs.
I am new to APIs and trying to get myself around it so my question may be silly. But why is the POST method used in this case and not GET? I mean we do not try to push data to the external service, right? We only want to get information out of it, don't we?
Hi. i just discovered this video and it's great. Thanks for that. I have a question: once the tool box created, is there any best practice to maintain it please ?
in the java code above where would you mention the end points is it when we try to instantiate the visual recognition object somewhere before the code in the video?
Out of all the tech giants putting out educational videos, IBM has the most visually appealing videos.
true, but the sound of the markers hurts me 😢
An SDK is just a pre-packages set of code (for a specific language) that you don’t have to write yourself. Sometimes free and sometimes you have to,purchase them. In the case of this video, he is suggesting a “API-Interaction” SDK a developer would use. There are all sorts of other SDK’s out there including things like an SDK to simplify building a User Interface.
What you describe sounds more like a framework to me. Isn't an sdk (software development kit) something you use during the development rather than during actual runtime? Like a debugger etc. If I'm wrong (which is totally possible), could you tell me where you would draw the line between framework and sdk?
@@ulicqueldromal isn't a framework like .NET an sdk anyway? (Idk though i could be wrong as well)
Thanks for that missing piece / clarification
@@ulicqueldromal sounds to me like he’s talking about templates in Wordpress. Especially the last sentence. So SDKs are themes ?
@@tresaidh3y90 no thats a framwork you literally just said it
Prior to 2000 and there is a period of overlap, API was synonymous with function calls to external libraries exposed by other modules. It could be local, in memory, inter-process or remote libraries (or set of libraries SDK), whether it was binary or textual. API's around 2000 became synonymous with HTTP SOAP Web Services, and circa 2012 became synonymous with REST Web Services.
I'm glad to see this comment cuz what's being discussed in the video is a Web API instead of a regular API. Nobody I work with seems to understand there's a difference there.
You nailed it!
Summary :
- API : enables a system to communicate with another (without having to understand the complexity of the other system)
- SDK : enables you to use APIs easily
well ... SDK's are actually code. It's actually instantiated, rather than being a protocol.
I didn't have the enough ryt now . To watch the full video.. Thanks for Summarising it. 😀
@@janglestick thank you mo one is saying what it actually is and you just nailed it. Its that simple.
1 Quick Question. Can a API not work properly without an appropriate SDK and vice-versa ?
@@bibekanandabhattacharjee952 My understanding is that sdk make it easier and faster to implement the api communication rather than writing code from scratch as it contains already all the methods needed to make api calls so we can just call the methods instead of writing the entire implementation. (Without reinventing the wheel)
I'm impressed that you wrote all this backwards, and didn't even screw up
There are editing softwares that can flip horizontally.
@@ganchen5555 lol
I'm impressed that you think he wrote all this backwards 🤣
The camera was filming behind a glass, and he was writing on that glass as per normal. The video was simply flipped like a mirror image.
He actually use his right hand to write
Even before I can concentrate on the subject he is explaining, my brain is lingering on the board and its depiction, it is so amazing
I do not understand why some people put a thumb down ?? This video is design to give an overview of technical concepts. It does an excellent job and reach it goal, it simplifies those technical notions without giving wrong info.
For the algorithm. Everyone who saw the thumbnail and thought why tf is this in my recommended
API is also the library of interfaces to a desktop application or program. For example, you can integrate a program to Excel by using its COM API Interface. API is basic, it's only an interface. An SDK is more complete as it can have library API interfaces AND Tools to work with a specific technology. For example, if you want to develop mobile apps from Windows, you will need an SDK for a mobile OS, which is a complete set of tools to compile the code to Native Mobile OS, a debugger, an IDE, etc. etc.
i am wondering how he learned writing reverse
I was just thinking that.
But, I think he wrote it just the way he always writes. But, in the editing software, the image is flipped horizontally...
Maybe the video is flipped?
The video is mirrored, so he is right handed and wear his watch on his left ARM ^^
he is a computer generated person
He's using a LightBoard. See ruclips.net/video/wCOuu0-o5YI/видео.html
When developing software, if you opt to create an SDK initially, design it in a way that allows for its use across multiple applications. An SDK is essentially a language-specific wrapper for APIs, so building distinct SDKs for similar applications is simply redundant. Additionally, remember that APIs are not constrained by language. Thank you.
i think this is the most clear and easy to understand video i've watched about api and sdk . love it, keep it up!!
Perfect. Was struggling with these terms. Helped me get a basic idea to build on.
Great video. Sound of that pen on glass though...uff shivering
I just go to 29 seconds where he finished the square for the dog, I can't even continue, it's like nails on chalk board for me.
i stop watch at this point
I agree. I had to discontinue the video bcz of sound it makes
I actually like that sound. It's nothing like nails on a chalkboard
Nails on a chalk board is pure hell.
I've watched many content about APIs. This video is definitely the best. Great job.
Without SDKs we would need to send API requests using low level HTTP commands in whatever language we use.
For example: Wanna talk to the Stripe API to get customer info using PHP?
Without an SDK you probably need Guzzle HTTP library to send several requests to the /customer/ endpoints while needing to pass authentication credentials each and every time in your code.
With their PHP SDK you aunthenticate once within your scripts and use the Customer object to get customer related data.
SDKs facilitate using an API but are not the API and are not guaranteed be offered by the service/company that published the API.
On the other hand, consuming the API using lower level commands offers us more control depending on how deep the SDK was implemented or not.
I highly recommend checking out Stripe’s APIs and SDK documentation to get a good example of amazing implementation.
Never knew programming was this easy. You have really open my mind to endless ways of developing solutions to problems.
Thanks Bro!
That's the idea. It should always be the guiding principles of good software. It's also great that the api or design when they are easy for the layperson to dive into the subject. Yes there is still a learning curve. If you look at search engines you dont ever had to think about issues about ranking or api or syntaxes almost never. Similarly, difficult concepts should be enjoyed by everyone. So there is a lot of work still.
Glad you're enjoying it
I don't understand shit
This guy is way ahead other explainers in youtube, nice charsima, speech and gestures, and nice looks
These IBM videos are NOTCHES above the google ones . Great stuff !!
This was absolutely simplified! Thanks IBM and amazing instructor
This channel is famous to make easy concepts complicated, hats off to you guys & keep up the good work.
I understand now what all this means, but sometimes you are just looking for simple definitions:
API is a URL that does something (retrieve info, change something or perform an action).
SDK is a file or files which have libraries that developers download and use in their proyects.
Then it comes everything else that you brilliantly explained.
I save you some time here:
API is if you make the requests yiursefl to an url to get, post, put etc. json data.
SDK is a sort of module written by the service provider which contains functions you can use to complete your task.
Example would be: upload_image("cat.png")
The down side of the SDK is its size. It has many funcrionality that one app might not use, also as SDK should be consistent over time, it should have the older versions which make them even larger over time. Also, as they run on our thread, they could have security issues, as well as malwares. It is better to make a good document for API vs an SDK. But big companies like to creare SDK to abscure data from developer. So never use an SDK unless it is open source.
Very Interesting. And here I thought SDK's was a great Idea.
worth noting that if the language has tree shaking, sdk size is not an issue
1.
10/10 in actually getting the point of the video across, keep posting content plz!
Dear IBM Cloud, you disturbed me with your creative board and the talented trainer. Due to the amazement, I could not concentrate on what he is teaching. You innovated a little more than what you need to.
Definitely loving these videos from IBM. Thank you for these!
이렇게 좋은 영상에 한글자막을 해주셔서 너무 감사합니다
근데 자막 너무 개떡같지 않나요??? 메소드를 방법이라고 하는데??? 통신을 의사소통이라고 하고 ㅋㅋㅋㅋㅋ 기계번역 수준...
Mr Beast?
Incredible instructional video! Congrats
Thanks for the explanation! That is the first presentation I see from an IBM person that goes directly to the point. Great.
I have been using api and sdk without knowing the terms for them! Thank you for the enlightenment!
Haha love this!
Who knew MrBeast would be teaching me about APIs and SDKs but this really helped!
this is pretty good movie clip to get basic understanding of between both. It is really helpful.
How the heck do you write like you write on a mirror...this guy is a genius!
Horizontal flip
The advantage of SDK is just to avoid handeling api requests and response , but in reality SDK will not reduce the extra code form application .
In simple word SDK is a sinthetic sugar over API
It was superb how he wrote his explanations in reverse 👏🏻👏🏻👏🏻
he didnt write in reverse. he reversed the video
Whoa, this is a exceptional vídeo about API and SDK topics, my english needs a upgrade, but thanks was necessary!
Thank you Natan from Ukraine.
God Bless You!
A nice short video by Nathan, but which gives a good insight on what SDK and API are. Thanks mate for your effort
The main difficulties of existing API multilevel systems are:
1.The difficulty of porting a program code from one API interface to another.
2.Loss of functionality upon jumping from lower layer to higher.
The fact hes writing backwards deserves a like.
Thanks ,a colorful presentation on api and sdk. very helpful.
You are most welcome
You looked like Mr. Beast! Nice explaination btw
true and also valletri bottas
Thank you for the easy and visually explanation.
Im not a native english speaker, the way you talk is amazing understable! Congrats!
Thanx for really breaking down into very simple to understand instruction
Wow, that is really simple straitforward explanation..
Great video, I think this helps remind us of what an API ‘actually’ is…I personally tend to use the term API when I should really be saying ‘SDK’.
I think another important concept to mention is that an API requires the logic to be hosted on 3rd party hardware, whereas SDK entails assemblies that you absorb as local references to your project and publish along with your build.
What is the difference between a SDK and a package then?
That screeching… I am dying here. Great content!
This is one of the best videos I've ever seen on youtube!!!
I love that this videos are dark moded.
Very nice video... The one I was looking for... This is the kind of demo I or I think common folks like me, look for when dealing with these software abbreviations littering the entire cloud development ecosystem. Keep posting great videos like these.
Very nicely articulated- I love it!
Thanks, Bala!
Wow, this is not the place I had expected to find a collab with Mr. Beast! What a versatile guy.
i kept looking at my sleeping dog thinking she was sick or something. apparently it was you. But THANK YOU, this video helps me a lot!
Hi, Thank you. It was great. please make more videos like this. best of luck.
I liked the API description but the SDK example was a bit muddy imo. Good work anyhow and appreciated.
Writing in reverse must be a struggle; all the more appreciation for the video!
See ibm.biz/write-backwards
Great breakdown Nathan.
Very succint. As a brief intro, it shines! Thanks, man.
API is low level communication layer with other application, SDK is higher level communication layer with other application. is am I right ?
You're definitely right. Sdk is made of api. Sdk leverage boilerplate, help you code with less effort. Sdk is a toolbox with screws, driver, humer. Api is what was used to make the toolbox and tools.
Rest-Api est a tool made by Apis.
@@vivienh.missamou208 Can we also compare it to a "method" in programming?
@@fern21 Yes just saying sdk as method is beautiful. even a layman can understand that instead of saying SDK
Sorry, but there seems to be some confusion here...
An sdk is typically a KIT for fx DirectX and the likes. Its purpose to give you a toolset on the box. It's also often including tools for advanced debugging like the Windows SDK. You work with a specific product to create something on that platform.
Api is an interface where for you ask a system or part of a system through a defined protocol to do some task for you.
Api exposes something through a specific paradigm whereas SDK's contains more than just a facade. That's more like lego.
REST is really a bad example, if we're being academic here. Cause we're talking about a very old paradigme that has been popularized. So, when people talk about Apis today, we tend to think HTTP, and not the likes of a C header file.
It's a matter of level of technology
Oh on a side note: I find it weird that this videos discusses a topic with no reference to C or C++ where these terms came to life and back in the hayday set many standards including this topic.
@@vivienh.missamou208 Is WinAPI (Windows API) in this case incorrect term as far as it gives access to Windows SDK?
These is a crestal clear example. I really appreciate your effort and method of education. great thank you as I wish to see more and more of this videos.
Very nice so a Partner API is a bridge between two business who share a common goal and have a relationship and trying to build something.
A nice explanation. And I loved the board.
Thank you for very useful videos guys! You're great!
This is a great video, I finally understand that difference
TLDR: an API is a specification. An SDK is an actual set of libraries, code and / or tools. There is usually overlap between the two.
Thanks for your helpful tips about SDK and API
This is an awesome video, but that is the doggiest cat I've ever seen.
Loved the video, too, but I will admit the dogcat kept distracting me. Glad I wasn't the only one! 🙂
The style of this tutorial is awesome.
This video gives me light for a design project of an app. Thanks!
I'm very impressed of his ability to write backwards...
It's amazing!
Probably he flipped the video after recording.
when mr beast teach valuable information.
A quick overview at the beginning then the explanation or the explanation then a quick a quick summary would make it more understandable.
this video blow my mind ,, great video
i love your explanation! easy to digest :) thank you!
Awesome explanation. I was struggling to understand it.
Awesome video! You made it pretty clear and straightforward for us! Thanks
I never knew Mr. Beast works for IBM lol
Thank you! amazing tutorial, clear and solid explanation.
Thanks for the video, the drawing is actually very helpful to understand between these two.
You're welcome, glad you like our video format! 👍
1min in the video, am like "gotta sub this channel". I love how calmly he explains things. Need more from this guy
The term API has been in use since the 1980s. Then it referred to callable functions to allow programmers to interact with the program product such as IBM CICS. In the 1990s we started to use the term with intra company systems. The customer information system at the bank where I worked had no screens of its own. Every action was performed by API calls.
It is wrong to say that API calls are standardised, The same API could be called using XML (SOAP when it became popular bespoke initially) over HTTP or MQ or natively from a message switch. There is no requirement to use JSON or XML.
It appears that the term API has been hijacked to mean REST, but that is only one implementation
They're both in the name.
API, Application Programming...Interface - a way of programming an application. An application is already built and is already running.
An SDK, Software Development...Kit. A set of tools (a kit) to develop software. This is independent from the application (a prebuilt binary). It's tools that you use to build a binary that does a specific thing. They usually consist if multiple APIs.
Thanks for making it so simple
This is a good explanation. Thank you!
I’ve loved this board since day one.
I’m glad that I’m not the only person who writes the letter of word first.
Very easy to understand API and SDK. Thanks
Great explanations sir. Thumb up
thanks a lot for this klarification its really help me to understant the concept of communication of an app
Great explanation! Thanks! :)
great and clear introduction to the terms
I am new to APIs and trying to get myself around it so my question may be silly. But why is the POST method used in this case and not GET? I mean we do not try to push data to the external service, right? We only want to get information out of it, don't we?
Well explained 🔥
Amazing Board technology and nice describing, easy telling story about mittens great job.. Brother
Hi. i just discovered this video and it's great. Thanks for that. I have a question: once the tool box created, is there any best practice to maintain it please ?
in the java code above where would you mention the end points is it when we try to instantiate the visual recognition object somewhere before the code in the video?
Both of these concepts where around 20-30 years ago, predating rest, html and java.
I'm interested in they way you film this video. Is there any special equipment or just pure mirror and dark background
Great video & excellent explanation 🙂