Top 6 Most Popular API Architecture Styles

Get a Free System Design PDF with 158 pages by subscribing to our weekly newsletter: bytebytego.ck....
Animation tools: Adobe Illustrator and After Effects.
Checkout our bestselling System Design Interview books:
Volume 1: amzn.to/3Ou7gkd
Volume 2: amzn.to/3HqGozy
The digital version of System Design Interview books: bit.ly/3mlDSk9
ABOUT US:
Covering topics and trends in large-scale system design, from the authors of the best-selling System Design Interview series.

[@ChrisAthanas]

The animations truly convey meaning and not extraneous This takes a lot of skill to get right Kudos

[@maximefourcadier408]

So true... +1000 for your comment

[@ShubhodeepDeveloper]

Everyone will agree, for a true Software Engineer, this channel is the most fruitful & addictive drug to learn new concepts in a crystal-clear manner.

[@hyperborean72]

speak for yourself, you id.ot

[@TheBelrick]

An excellent summary video.

[@georgepandiaraj2857]

I am absolutely impressed with the simple, clear, and elegant illustrations! It’s superb! Thank you for sharing.

[@igordasunddas3377]

This is awesome, the animation is meaningful and helpful while also being pleasing to the eye. Thank you!

[@kriegeadler]

Amazing animations and outstanding explanations. I wish I had this sort of educational videos years ago! Thank you very much for sharing this. You have earned a new follower!

[@kevikiru]

This is a surprise. I was debating with myself whether to watch this video because I was worried that it might go right over my head. I am happily surprised by how understandable it was!

[@systemBuilder]

the technologies on this page are at somewhat different layers of the protocol stack. SOAP is a pure encapsulation format (last I looked which was long ago) that can run on any transport, RESTful is HTTP-dependent, as is WebSocket, which does not define an encapsulation for transactions it just connects TCP sockets together on an HTTP proxy, gRPC is a protocol compiler meant to translate a language interface (think of it like a C++, Python, or Java interface) into the code to create the binary bits on the wire (or wireless), a process called marshalling or serialization / de-serialization. gRPC is transport independent but typically runs on TCP or UDP. GraphQL is a language that can specify json schema queries and it can minimize large transactions on the connection - good for phones or bandwidth-limited devices.

[@alfonsobaqueiro]

Don't be so purist, this is just a light explanation of architectural API styles, not an indeep study where you must talk about SOAP transport independence for example.

[@higgsbozon]

@@alfonsobaqueiro so out of all the useless comments here (which you will find on 99% of the any video on youtube), you chose to deride the one actual useful and super important comment which actually tells a knowledge seeker where to go next? This is why most KZbin content is filled with garbage.

[@SadSadDeadM]

I really miss in-depth videos :(

[@abenezerseleshi2137]

YES WE DO

[@mango4199]

I bet the main reason why there haven’t been more videos like this lately is due to the whole gold-rush like event over the past two years where everyone under the sun wanted to cash in on becoming a developer quick and make 6 figures. So what do KZbinrs need to make to attract this new crowd? Not in-dept videos, beginner friendly videos. Surface level explanation videos.

[@The-KP]

​@@user-oi9gi7kl2pIn this short video we learn little about each API type. And there is a multitude of other API styles and variations in use that aren't mentioned. I do wish he'd go into more depth-perhaps the compromise would be continuing the short intro videos like this, but then go into more depth in longer videos that branch off on one of each API type

[@VincentJenks]

To me, BBG is brilliant in this respect. There’s so much for us to know, learn, and keep up with. These are great mental “bookmarks” to point you towards pinpoint searches, to find the depth you need elsewhere. I get what you’re saying though. A great addition in this channel, would be links to in-depth, or just follow-up videos with more depth on each topic, alone. Then you could go down each rabbit hole from the high level video, as needed.

[@magichatake]

@@VincentJenks yeah man, these videos are helping me find which way should I go now. Actually, I work with API Gateway management but I'd like to improve my skills and these superficial videos help me a lot

[@nm3547]

You were very clear, visibly clear, and straight to the point. Thanks for this video and explanation.

[@deutschWallah]

Dear Alex, You are one of the best programmers and teacher I have seen till now on KZbin.

[@mintoo2cool]

i cannot appreciate this channel enough. ❤️

[@pooja0407]

Amazing video for an overview understanding of different API styles. I am a Data Engineer with 3 years of experience and I got a similar question on why I used REST API instead of SOAP or any other APIs. This video helped me there to explain my POV. Huge respect to the content creator who seamlessly explained all the 6 concepts in a niche manner!

[@samjones0320]

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!

[@rl6382]

Please make more videos. You're literally the GOAT

[@yomamasofat413]

great video. Simple easy to understand, straight to the point

[@ChineduRufus-s9f]

This is straight forward and clear

[@Mrcodewarrior77006]

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. 👍

[@tylascraig9306]

Thanks for the recommendation. I added both books to my Amazon reading list.

[@theBillonaire]

Great Video and Animations are very understandable

[@conrad707]

Great content. Succinct, with very helpful illustrations. Well done! You have a new subscriber

[@ronpdf2084]

I am from Brazil. I loved your video!!!

[@herwin1417]

Thanks for making high quality education video free

[@nini_kys]

Beautiful animations!! Amazing commentary that really compares so well.

[@ambikeya_tech]

Insightful breakdown of API architecture styles! Appreciate the concise overview. Valuable resource for understanding different approaches to building APIs. Thanks for sharing!

[@experience_kingsley]

Loved this! I am not heavily involved with APIs but wanted to learn more. This was perfect. Thanks!

[@mikemjlove4988]

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

[@LucyPLM]

Within multiple separate services? Isnt that just websockets?

[@Rio-by1eh]

Great summary ✅

[@FanYang_FAN]

Alex, you are amazing~

[@gkalchev]

Spot on. Short, clear, and understandable. Congrats

[@gagAMinute]

Wonderful video!! TYSM 👐

[@rammehar5531]

wonderful Sir, You doing great Job, I always loves to watch your videos

[@xscade]

Thank you so much for such an informative video, This will help upcoming engineers understand when to use what.

[@someoneelse6976]

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

[@9expert]

Cool ! Thank you.

[@eliaszeray7981]

Great & informative ! Thank u.

[@Rogueixpresents]

bro i love your brain, thank u for this !!!

[@whatdaro]

great succinct straight to the point no fluff... excellent content! subbed.

[@tempest3327]

You are going to be a big channel, lots of love and support ❤ Keep up the great work

[@praveen8559]

appreciate your effort in bringing these videos, simplifying concepts, kudos to your work!

[@kaushalkumar6666]

I am overwhelmed by this video Thank you so much

[@aunghtayoo337]

Thanks for the quality content.

[@jg4093]

Really helpful the way this was explained thankyou!

[@uultaiarstankulova7808]

great explanaition, thanks!

[@chasingmillions8584]

Thank you - this was so helpful!!!

[@andreasvanbergen9696]

👍Great video! Thanks for sharing...

[@diamonddunyasi4945]

Thank you very good summary🙂

[@parsalotfy]

great video, thanks

[@officialismailshah]

Never regret subscribing your channel great content 🎉🎉🎉🎉

[@TeverRus]

Real nice! Thank you :)

[@gauravbisht1949]

Top-notch explanations

[@Vykhari1]

Thank you. It helps to understand the basic differences.

[@konkerouf]

I'd like to add one note on websockets and webhooks. Webhooks require for the subscribers to be accessible (ie: not hidden behind a gateway) for the publisher to contact them. Websockets dont have this problem, as the subscribers are initiating the connection. Because of that, websocket is also a good solution for async events notification when the subscribers are not accessible / "open to the web" machines

[@irfansiddiqui9458]

Love this!

[@florecista1]

Great video! Bravo!

[@LuisPerez-mw5kl]

Excellent explanation, simple and clear.

[@MrPlaiedes]

Perfect. Thanks!

[@pranavbhagwat1734]

Very helpful and to the point, thank you for this excellent content!

[@olegstrekachev6734]

Great job at explanation and presentation

[@kengounited]

Clean, neat, and to the point.

[@shuhratdoniyev2537]

The best video. It would be great if you could please provide an in-depth video on the network OSI model.

[@7guitarlover]

Love the animations !

[@AlexxXRecorD]

Cool, thanks for explanation!

[@havaskorwebdasturchilar3809]

Thanks bro, it's very useful information.

[@jubiliudu]

Just amazing.

[@Akiiiii01820]

these architectures are protocols, right? and thank you for sharing this!

[@theBATfamiliar]

Thank you so much for sharing your knowledge :)

[@charlesopuoro5295]

Thanks always.

[@Maouww]

I do like these videos!

[@aradhya1712]

Good video, to the point

[@jfroco]

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).

[@dclxviclan]

Woooow, powerful video ❤

[@AthelstanEngland]

Excellent!

[@NewHorizon-v9p]

Perfect, but there is also Event Source which is mainly used for notifications system (push) one direction from server to client.

[@RiskyMeal]

A damn good video... This is a damn good video!

[@codegreenie3429]

I use Restful & Webhook in my software. Thanks for this video

[@DineshS-c5c]

Thanks for the useful information

[@k-r6465]

Thank you .. please give us some examples to deeply understand how to use API's

[@colinliew1400]

You sir have helped me understand a lot of things. Love the channel

[@sachin2440]

Amazing stuff

[@t1m9mofficial]

You are awesome!

[@jerryanyu8467]

视频动画真的不错。谢谢Alex!!

[@anthonychand9501]

Love the animated diagram!

[@osh2023]

Thank you.

[@undudeme]

Awesome video.

[@pratikchavan3603]

hey this is perfect

[@acronproject]

Thanks for this

[@NeverCodeAlone]

Super good movie. Thx a lot.

[@adiprada5818]

Great videos to explain about the distinction between API styles. However I am not sure if WebHook is an API style. It is more like notification or part of event-driven architecture and usually implemented using RESTful API. Also, WebSocket is more like a communication protocol rather than "API".

[@joshyboy152]

Great video

[@Diegoad1]

Thank you!

[@fr3nzy1111]

I love your videos!

[@TuấnNguyễn-s3h9f]

the greate video 🎉

[@my_yt666]

There is also tRPC and OData. WebSocket is not really a style, else you should include SSE.

[@ebragimovic]

Outstanding video as usual! Please arrange another video for data migration strategies

[@begginercoding.3919]

well explained

[@amirnathoo4600]

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.

[@LucyPLM]

So... websockets?

[@amirnathoo4600]

You wouldn’t use websockets directly as a pub/sub. You’d have to implement something on top of that. MQTT uses websocket as an underlying protocol to communicate with browser applications. In a distributed architecture you can also use other Pub/Sub mechanisms like Kafka or RabbitMQ.

[@amber4131]

Happy coding! I like it!

[@en_el_contexto]

exelent!!!!

[@rbelatamas]

thanks ❤

[@rohulahadi3990]

🔥😍 thanks