Top 6 Most Popular API Architecture Styles 

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.

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

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.

I really miss in-depth videos :(

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!

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

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!

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!

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

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

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

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

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

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

Spot on. Short, clear, and understandable. Congrats

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

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

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

I am overwhelmed by this video Thank you so much

Thank you. It helps to understand the basic differences.

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

Thank you - this was so helpful!!!

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

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

Really helpful the way this was explained thankyou!

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

Excellent explanation, simple and clear.

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

Clean, neat, and to the point.

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

This is straight forward and clear

Thank you for sharing this much of information.

Thanks for making high quality education video free

Never regret subscribing your channel great content 🎉🎉🎉🎉

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

great explanaition, thanks!

Thanks for the quality content.

Thank you very good summary🙂

Love the animated diagram!

Great job at explanation and presentation

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

Good video, to the point

Please make more videos. You're literally the GOAT

Great summary ✅

Love the animations !

Thanks bro, it's very useful information.

Thanks for the useful information

Great Video and Animations are very understandable

Wonderful video!! TYSM 👐

Cool ! Thank you.

great video, thanks!

Perfect. Thanks!

Cool, thanks for explanation!

Top-notch explanations

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 👍

Thank you

Real nice! Thank you :)

Great video! Bravo!

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

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

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

I love your videos!

Love this!

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

Thanks for this

Thank you!

👍Great video! Thanks for sharing...

Woooow, powerful video ❤

Thanks always.

Excellent!

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

Super good movie. Thx a lot.

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

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

Amazing stuff

hey this is perfect

I do like these videos!

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

Thank you so much for sharing your knowledge :)

thank you

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

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

Awesome video.

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

masterful

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

well explained

Great video

🔥😍 thanks

You are awesome!

thanks ❤

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!

Amazing

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

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

Love it :)

love this. im bout to be 10X

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

Great!

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