Top 6 Most Popular API Architecture Styles

Get a Free System Design PDF with 158 pages by subscribing to our weekly newsletter: bytebytego.ck.page/subscribe
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.

[@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.

[@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.

[@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

[@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!

[@samjones4327]

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!

[@georgepandiaraj2857]

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

[@nm3547]

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

[@neeleshgupta3491]

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

[@praveen8559]

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

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

[@rajeswaril3931]

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!

[@gkalchev]

Spot on. Short, clear, and understandable. Congrats

[@igordasunddas3377]

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

[@tempest3327]

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

[@whatdaro]

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

[@yomamasofat413]

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

[@kaushalkumar6666]

I am overwhelmed by this video Thank you so much

[@ambikeya_tech]

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

[@chasingmillions8584]

Thank you - this was so helpful!!!

[@pranavbhagwat1734]

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

[@Vykhari1]

Thank you. It helps to understand the basic differences.

[@colinliew1400]

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

[@kengounited]

Clean, neat, and to the point.

[@tylascraig9306]

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

[@someoneelse6976]

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

[@jg4093]

Really helpful the way this was explained thankyou!

[@LuisPerez-mw5kl]

Excellent explanation, simple and clear.

[@7guitarlover]

Love the animations !

[@officialismailshah]

Never regret subscribing your channel great content 🎉🎉🎉🎉

[@aunghtayoo337]

Thanks for the quality content.

[@rammehar5531]

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

[@user-be2yu6id9r]

This is straight forward and clear

[@anthonychand9501]

Love the animated diagram!

[@uultaiarstankulova7808]

great explanaition, thanks!

[@rl6382]

Please make more videos. You're literally the GOAT

[@BestURLShortenerBioPageQRCode]

Thank you for sharing this much of information.

[@gagAMinute]

Wonderful video!! TYSM 👐

[@theBillonaire]

Great Video and Animations are very understandable

[@herwin1417]

Thanks for making high quality education video free

[@florecista1]

Great video! Bravo!

[@TeverRus]

Real nice! Thank you :)

[@guodonghu286]

great video, thanks!

[@conrad707]

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

[@olegstrekachev6734]

Great job at explanation and presentation

[@user-xb7bc5eo1w]

Thanks for the useful information

[@fr3nzy1111]

I love your videos!

[@Rio-by1eh]

Great summary ✅

[@AlexxXRecorD]

Cool, thanks for explanation!

[@MrPlaiedes]

Perfect. Thanks!

[@diamonddunyasi4945]

Thank you very good summary🙂

[@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?

[@ronpdf2084]

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

[@9expert]

Cool ! Thank you.

[@SaurabhOKumar]

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 👍

[@scienc3tv]

Great video! Great animations! (for curiosity are you using Manim for animation?)

[@aradhya1712]

Good video, to the point

[@gauravbisht1949]

Top-notch explanations

[@irfansiddiqui9458]

Love this!

[@dclxviclan]

Woooow, powerful video ❤

[@andreasvanbergen9696]

👍Great video! Thanks for sharing...

[@acronproject]

Thanks for this

[@havaskorwebdasturchilar3809]

Thanks bro, it's very useful information.

[@AthelstanEngland]

Excellent!

[@Rogueixpresents]

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

[@Diegoad1]

Thank you!

[@shuhratdoniyev2537]

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

[@Maouww]

I do like these videos!

[@charlesopuoro5295]

Thanks always.

[@sachin2440]

Amazing stuff

[@undudeme]

Awesome video.

[@codegreenie3429]

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

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

[@adarknight9830]

Thank you

[@ebragimovic]

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

[@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".

[@cd-stephen]

masterful

[@T1m9m]

You are awesome!

[@joshyboy152]

Great video

[@NeverCodeAlone]

Super good movie. Thx a lot.

[@theBATfamiliar]

Thank you so much for sharing your knowledge :)

[@rohulahadi3990]

🔥😍 thanks

[@satishreddymsk]

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

[@user-xj6fp8mc1o]

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

[@user-ds4qz1mc3t]

Great Explanation!! What tools did you use to create the animations?

[@pratikchavan3603]

hey this is perfect

[@k-r6465]

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

[@karthikr5884]

Love it :)

[@begginercoding.3919]

well explained

[@jerryanyu8467]

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

[@praweewongsa]

thank you

[@my_yt666]

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

[@wxIyz]

Amazing

[@PieJee1]

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

[@mormatus]

Yeah, actually problems with caching defeats the argument about it being "more efficient", because depending on the app, you could make it many times less efficient instead

[@rbelatamas]

thanks ❤

[@amazekhashaa7309]

Great!

[@RunningtoCatchMyBreath]

love this. im bout to be 10X

[@user-ti7uk4bj8u]

the greate video 🎉

[@TheRavageFang]

What's the reason for not using Server sent events? Keeping one connection always open? Or are there more drawbacks?

[@gusteven3937]

It's very useful for, I can learn more with the assiento of ChatGPT.