Top 6 Most Popular API Architecture Styles

Video quality	The size	Download

Информация о Top 6 Most Popular API Architecture Styles

Название	:	Top 6 Most Popular API Architecture Styles
Продолжительность	:	4.21
Дата публикации	:
Просмотров	:	492 rb

Perfect Thanks!
Comment from : MrPlaiedes

Excellent explanation, simple and clear
Comment from : Luis Perez

appreciate your effort in bringing these videos, simplifying concepts, kudos to your work!
Comment from : Praveen

Are they TSP or UDP?
Comment from : Igor Morozov

Top-notch explanations
Comment from : Gaurav Bisht

Thank you so much for sharing your knowledge :)
Comment from : theBATfamiliar

Thank you for sharing this much of information
Comment from : Shorten World Platform

I like it
Comment from : Krishna Murthy Madaraboina

Thanks always
Comment from : Charles Opuoro

I really love your graphics! ❤ It's one of the reasons I just watch them one by one :-))
Comment from : Someone Else

signalR ?
Comment from : Federico Tomadin

Complex systems may even have several APIs of different architecture styles
Comment from : Arthur Khazbs

How did you build these beautiful animations??
Comment from : Cause Neffect

How about Firebase DB using JSON to handle the real time data?
Comment from : Mukhtar Otarbayev

Useless
Comment from : Work Pony

Amazing stuff
Comment from : Sachin

There is really no reason I can think off to use SOAP in a new project today, a REST API is what you most likely want to use instead
Comment from : MΛX

1:33 what's Twitter?
Comment from : Josh W

Thank you please give us some examples to deeply understand how to use API's
Comment from : K-R

You are awesome!
Comment from : t1m9m

Take this misinformation down 💀
Comment from : Kalahari

视频动画真的不错。谢谢Alex!!
Comment from : Jerry An Yu

Thank you very good summary🙂
Comment from : Diamond dunyasi

Can any one tell my how these animations videos are created? What tools? They are amazing
Comment from : peaceloverchap

Nice snapshots Could you please explain grpc in details ?
Comment from : Rajib Das Gupta

Spot on Short, clear, and understandable Congrats
Comment from : Georgi Kalchev

aaaaaaaaaand it makes sense to me now 🙏🏾
Comment from : Ben12♓

Wow that is a great explanation that has enough detail to understand the differences but short enough for me to watch between work tasks Good enough to get my subscription and that doesn't happen often
Comment from : Snoogle Hound

Great job at explanation and presentation
Comment from : Oleg Strekachev

What tool is Sahn using for this animated design?
Comment from : GODWIN OJIMA ATTAH

1:28 "Hello, Eorld" lol Eorld???? brSorry, I am a Tester; couldn't help it! 😜
Comment from : Syed Armaghan Hassan

Do you even know what "architectural style is"? You barely mentioned few (not even all common) COMMUNICATION styles, not architectural styles! Archictectural styles are much more than communication, they have much deeper consequences and benefits, are things like monoliths, microservices, event sourcing, 3-layered architecture, onion architecture, actor model, etc
Comment from : Irek M

bro i love your brain, thank u for this !!!
Comment from : Skoozle

great explanaition, thanks!
Comment from : Uultai Arstankulova

What software do you use for your presentation please
Comment from : AZ

Wonderful video!! TYSM 👐
Comment from : Comic Chronicles

Love this!
Comment from : Irfan Siddiqui

Can you tell how you made this vidoe with diagram moving? very impressive
Comment from : テスラでTESLA 【AlohaJayOfficial】

Technically, these are the 6 most popular Web API architectures SOAP and gRPC over pipes are pretty much the only ones used in desktop systems
Comment from : The Werewolf

Comment from : Vlad Comarlau

mqtt, sse, rsocket, quic
Comment from : sumanta ghosh

what does this information have common with System Design? it's actually mostly about Web-APIs System design is totally another topic that stands much above any APIs or computer technologies in the abstraction level Neither these are Architecture Styles This is just a bunch of random concepts: network protocols and programming approach The information in this video is misleading
Comment from : Folivo

Beautiful animations!! Amazing commentary that really compares so well
Comment from : Neelesh Gupta

What about Server Sent Events? Can we consider it as API Architecture Style?
Comment from : Mateusz Krukowski

Excellent!
Comment from : Athelstan

Very good, concise and accurate explanation of the most frequently used types of APIs Awesome job! I'll be directing my students to your site 👍
Comment from : Herb Garcia

Can grpc be used over internet instead between microservices? is it a good design choice?
Comment from : catstevens01

Great video
Comment from : Josh

Missing one of the most important API architecture style: PubSub messaging architecture This is typically found in IoT applications using protocols such as MQTT It can also be found as communication style between micro services
Comment from : Amir Nathoo

👍Great video! Thanks for sharing
Comment from : Andreas Van Bergen

A damn good video This is a damn good video!
Comment from : Risky Meal

are SOAP really for enterprise or just because entrerprise has this as legacy implementation?
Comment from : rickvian

well explained
Comment from : Begginer Coding!!!😀😀

Clean, neat, and to the point
Comment from : physicsninja

The explanation with meaning animations made the concepts to understand easily like👍 curiuos to know what tool/software being used to make these animations?
Comment from : Satish Reddy

Thanks for this
Comment from : Acron Project

I picked up GraphQl in a day, I doubt it has a steep learning curve
Comment from : Ikenna Paschal Obieze

Broo, be a little bit more energetic, please
Comment from : Ayub shaik

Real nice! Thank you :)
Comment from : Илья Барсуков

Other issues with graphql is lack of caching, and your frontend and backend become very tightly coupled as changing property names means you have to update both This becomes even nore trouble if you have more frontends
Comment from : PieJee1

The script seems AI generated
Comment from : :chart_with_downward_trend:

I do like these videos!
Comment from : Maouw

Woooow, powerful video ❤
Comment from : Dclxvi Clan

I use Restful & Webhook in my software brbrThanks for this video
Comment from : @codegreenie

thanks ❤
Comment from : rbelatamas

Deep explain for Rest and Graphql please
Comment from : PIP POP

useful
Comment from : Abbos Zoirov

Nice one ! Can you explain webrtc is in which category?
Comment from : Ali Bahrami

Great video! Bravo!
Comment from : florecista1

Mi mayor error fue comprar sin saber y vender sin saber, pero no puedo negar que es experiencia que sirve mucho
Comment from : Hernan Borrajo

Awesome video
Comment from : undudeme

Thanks for the quality content
Comment from : Aung Htay Oo

Great Video and Animations are very understandable
Comment from : The Soul Of Life

APIs can be designed with Web Sockets
Comment from : Ajay Managaon

Used them all, is there nothing new? how about kafka, iot, mosquitto micro services?
Comment from : planktonfun

thank you
Comment from : Prawee Wongsa

I believe you might be conflating API architectures with API implementations For instance, GraphQL could be categorized along with any variant of SQL or Redis commands, as they all facilitate data retrieval using a query language Similarly, WebSocket could be grouped with other session-oriented, two-way communication alternatives, such as basic TCP sockets, or you could hava mentioned various flavors of RPC Additionally, RESTful and SOAP could be classified together under the umbrella of web services that employ the request/response pattern Webhooks may possibly fit into this same category, although I'm not entirely certain Lastly, you appear to have omitted queuing or messaging/queuing systems like Apache Kafka (very popular)
Comment from : jfroco

Thank you very much for sharing, I not sure about MQTT is which one API?
Comment from : NirutG

Great distinctions, It's a unique video Thanks for clearing these out Additionally, can you present them in clear distinct points based differences on a single TABLE for all these APIs under various grounds? Because it looks like some of them overlap one another under certain criteria It will be great to have a clear point based differentiation represented on a table! Thanks It will be great to see them stand together while comparing before the eyes under various domain based scenarios & environments Thanks 👍
Comment from : Saurabh Kumar

Great!
Comment from : Amaze Khashaa

perfect if turn the speed to 125😀
Comment from : skyskyblue

Thank you It helps to understand the basic differences
Comment from : Human

Nice video, quick question: I have a dumb dev ops enginieer that wants to do everything on top of kafka Is kafka part of one of those architectures or is a new one?
Comment from : ariel batista

the greate video 🎉
Comment from : Tuấn Nguyễn

Great video!brGreat animations! (for curiosity are you using Manim for animation?)
Comment from : amaw in person

Happy coding! I like it!
Comment from : Amber

Please make more videos You're literally the GOAT
Comment from : RL

tRPC ?
Comment from : beijing9y

I am overwhelmed by this video Thank you so much
Comment from : Kaushal Kumar

I have been working for financial services for almost 15 years and in my experience, SOAP is 100 obsolete now It is mostly replaced by REST
Comment from : Krishna Kumar

There's also Serverside events Which may not be an architecture for API but it does opens up an option to send unidirectional data without having to touch websockets
Comment from : Mike MJlove

I would like a comparison between gRPC and jsonRPC
Comment from : Fergus 13

i understood all well , have used before , except for gRPC, doesn't click for me till now i understand microservices architecture, and how to build apps based on microservices(smallest units each with its own service) how does gRPC come into play ? give a case example; i stand to be corrected, thanks in advance!
Comment from : serial killer

Awesome video and tutorial!! I really appreciate the way you break these architectures down so that I can get a great high level understanding of them!! Outstanding! Be well, be safe and Cheers!
Comment from : Sam Jones