I have had a hard time finding information on just a birds eye view of the different types of API technology and how they basically work until I watched this video which is the best I have ever seen on this topic by far.
Your videos are absolutely spot on the topic with a sleek representation of content. The travel industry based explanation is a cherry on top. Keep going guys!
OMG this video explained so many of my Questions about rest, grapql etc. The animations and the video cut is top-notch too. This comment may seem ironic or exaggerating, but I really am presently surprised. 😭
I absolutely love your video! Your content is always informative and engaging, and I appreciate the effort you put into it. However, I find the background music a bit distracting at times. It would be great if you could consider removing it or lowering its volume to make it easier to focus on your amazing content. Keep up the fantastic work!
Is encrypting each message that big of a benefit of SOAP if you already using SSL, which essentially does that same thing but just for the whole payload?
Talking about WS-SECURITY, it's stated that, the encrypted body can only be accessed if you have a token in header. How is this different from using OAuth or any token based security in REST?
SOAP WS-security includes the mechanisms for encrypting the whole message. OAuth and JWT are authorisation mechanisms. They aren’t designed for message encryption and you have to find your own ways to encrypt the message body or use an SLL/TLS protocol when sending the message.
I thought learning curves were amount learned (Y axis) and time to learn (X axis) so a shallow learning curve would be something hard to learn (lots of time to get more info) and a steep learning curve would be easier (less time to learn more info). But I could be wrong.
it just refers to that you have to learn a lot -> lots of incline; whereas a shallow learning curve means that you do not have to learn that much to understand. the time, in my opinion, is no object in this allegory
@@magdastein5580 I have always struggled with this. But I like it. So the Y axis goes from zero learned to easy to learn, medium to learn and hard to learn. Where as I was thinking it went from learning zero of the material, to 100% of the material.
It depends on the specific API you need. GDSs offer separate APIs for checking flight status or seat canceling. Sabre mostly uses SOAP and REST APIs. The same goes to Amadeus. Travelport provides SOAP and XML APIs. You can find the required API by the links: developer.sabre.com/product-catalog?f%5B0%5D=product_type%3Asoap_api_reference newmy.travelport.com/web/developer/travelport-universal-api developers.amadeus.com/
![Blox Fruits Dragon Rework Update [Full Stream]](http://i.ytimg.com/vi/EqDAp8udhm0/mqdefault.jpg)
Sources:
[ 1 ] xml-rpc.com
jsonrpc.org
grpc.io/
[ 2 ] www.tutorialspoint.com/soap/soap_envelope.htm
[ 3 ] facebook.com/altexsoft/posts/2463168813706531
[ 4 ] developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_quickstart_intro.htm
[ 5 ] www.restapitutorial.com/lessons/restfulresourcenaming.html
stackoverflow.com/questions/54653110/rest-data-format
[ 6 ] developers.booking.com/api/commercial/index.html?version=2.7&page_url=usage-information
[ 7 ] telegram.org/faq#:~:text=Telegram%27s%20special%20secret%20chats%20use,on%20their%20devices%20of%20origin.
[ 8 ] 100daysdx.com/28/
[ 9 ] engineering.fb.com/2015/09/14/core-data/graphql-a-data-query-language/
[ 10 ] graphql.org/learn/schema/
www.apollographql.com/docs/tutorial/schema/
lucasconstantino.github.io/graphiql-online/
[ 11 ] www.assurantlabs.com/blog/2020/02/23/graphql-in-mobile-development/#related-benefits-of-graphql--libraries
[ 12 ] graphql.org/users/
[ 13 ] www.altexsoft.com/blog/engineering/what-is-soap-formats-protocols-message-structure-and-how-soap-is-different-from-rest/
[ 14 ] www.canadapost.ca/cpo/mc/business/productsservices/developers/codesamples.jsf
www.canadapost.ca/cpo/mc/business/productsservices/developers/soap/codesamples.jsf
High quality work, even has the refs...thanks!
Whoever is making these videos. Please never stop. It's hard to find such sleek and useful content. Your channel is a hidden gem.
I feel that a lot of effort was made when creating this video. Pretty good content!
У вас такий крутий канал і контент увесь по суті, а не переливання з пустого в порожнє! Дякую за вашу роботу!!!
Дякуємо :)
I have had a hard time finding information on just a birds eye view of the different types of API technology and how they basically work until I watched this video which is the best I have ever seen on this topic by far.
struggled a bit with all the api types - but this video gave me the insight I needed
I took me more then an hour to watch this video along with goggling some things mentioned in it and making notes. It is sooo good. Thank you
Best gem on youtube. Pls keep doing videos like this. Nothing more nothing less.
All anyone can ask for is learning content as good as in this video. ♥️ Love it.
Thanks for your feedback, really appreciate it ❤️
that was excellent. I now feel confident not just understanding API but their history and pro`s and cons. thank you
Excellent. Full of useful information, concisely put with no waffle. Great Job 👍
Amazing video. I’ve been searching for a simple explanation like this. I don’t know why there is only info about REST
THANKS , great and simple explanation for a beginner
Glad you liked it
Your videos are absolutely spot on the topic with a sleek representation of content. The travel industry based explanation is a cherry on top. Keep going guys!
Much appreciated for such lovely feedback, thanks
Excellent content which clearly explains the different forms of API and why each of these came into existence over time. Great work!!
Wow thank you for this very useful video!
Best explanation ever!
Thank you
Thank you lot of information shared Ina comprehensive way
Amazing vid. It goes to the point. Thanks for sharing. I can really see you made a great effort to create this content.
Really well-presented! Thank you, easy to follow by non-technical people too :)
OMG this video explained so many of my Questions about rest, grapql etc.
The animations and the video cut is top-notch too.
This comment may seem ironic or exaggerating, but I really am presently surprised. 😭
Amazingly clear video keep making this!
Glad you enjoyed the video, thank you for the feedback)
Excellent and really helpful content.
Terrific video and explanations. Thank you
Very good explanation.
This video contains many articles with sometimes vague answers in one flask
Used to think api was a kind of module to you needed. Now this cleared things up for me.
👍
Fantastic video, thank you for your effort!
Happy to hear that you found our video fantastic, thank you for the feedback ❤️
I absolutely love your video! Your content is always informative and engaging, and I appreciate the effort you put into it. However, I find the background music a bit distracting at times. It would be great if you could consider removing it or lowering its volume to make it easier to focus on your amazing content. Keep up the fantastic work!
Great video! Wished it went into more detail with gRPC, PROs/CONs were not discussed.
great work explaining this topic
Good content and the presentation was lovely. Will be staying tuned to the channel for sure.
Excellent video!
Thank you.
What a presentation! great and clear one
Is encrypting each message that big of a benefit of SOAP if you already using SSL, which essentially does that same thing but just for the whole payload?
Outstanding video, congratulations and thank you
cool, just what I needed to know. Thanks.
Glad to help 😊
Absolutely loving this great video!
Super helpful video
succinctly explained!
You underrated rpc and protopuf in my opinion.
This was great. Thank you!!
very well made. thanks
Sooo….soooo…. gooood 👌👌👌👌👌
Excellent...
Best video I've seen
Such an awesome video!
Awesome content!
Congratulations, this is excellent content! :)
Somehow sharing on LinkedIn gives a 414 error response. Gets difficult to share it.
Talking about WS-SECURITY, it's stated that, the encrypted body can only be accessed if you have a token in header. How is this different from using OAuth or any token based security in REST?
SOAP WS-security includes the mechanisms for encrypting the whole message. OAuth and JWT are authorisation mechanisms. They aren’t designed for message encryption and you have to find your own ways to encrypt the message body or use an SLL/TLS protocol when sending the message.
@@AltexSoft Thanks for the clarification & awesome video!
this was beautiful
I thought learning curves were amount learned (Y axis) and time to learn (X axis) so a shallow learning curve would be something hard to learn (lots of time to get more info) and a steep learning curve would be easier (less time to learn more info). But I could be wrong.
it just refers to that you have to learn a lot -> lots of incline; whereas a shallow learning curve means that you do not have to learn that much to understand. the time, in my opinion, is no object in this allegory
@@magdastein5580 I have always struggled with this. But I like it. So the Y axis goes from zero learned to easy to learn, medium to learn and hard to learn. Where as I was thinking it went from learning zero of the material, to 100% of the material.
great content
My only complaint about this video is that the background music was soo good I kept getting distracted lol
.
Great job!!!
Well done!
Which API used by GDS systems?
It depends on the specific API you need. GDSs offer separate APIs for checking flight status or seat canceling. Sabre mostly uses SOAP and REST APIs. The same goes to Amadeus. Travelport provides SOAP and XML APIs.
You can find the required API by the links:
developer.sabre.com/product-catalog?f%5B0%5D=product_type%3Asoap_api_reference
newmy.travelport.com/web/developer/travelport-universal-api
developers.amadeus.com/
@@AltexSoft Thank you...
Background music incoming in 7:20 is killing me XD
Don't die, better dance 💃
So, SOAP - a bit improved XML-RPC? And REST is a RPC over HTTP? And so on... Everything is RPC?
Excelent
Not convinced that the rpc definition is correct.
Excellent and really helpful content.
great content
Thanks for feedback ☺️
Excellent and really helpful content.
Great content