Top 6 Most Popular API Architecture Styles

38 thoughts on “Top 6 Most Popular API Architecture Styles”

• Really helpful the way this was explained thankyou!

• Thanks for making high quality education video free

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

• I wish i was as smart as you sir

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

• Please make in depth videos

• Where is fetch api categorized here?

• I understand that this explanation is very shallow and high level but still there are significant lacks, e.g. GRPC is also bidirectional, and what is important uses HTTP 2.0. the main disadvantage is poor support in non mainstream languages. SOAP is a legacy, and mostly used by bloody enterprise, every developer hates it and XML in particular. Nothing said about JSON-RPC. Nothing said about message busses which are also could be considered as an API styles. This shows that IT landscape overflawn by such an "experts". The ability to draw nice pictures doesn't make you an expert.

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

• Okay. I wanna say SOAP should be avoided. Whatever SOAP can do, REST can do better. There's no "stability and reliability are keys" here. Ok show me how can SOAP more stable/reliable than REST?

• Adding title for each would be helpful, great video otherwise

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

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

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

• SOAP and RPC are not APIs at all – – they are examples of [web services] and are completely different than REST API, GraphQL, WebSocket, Webhook

  you can implement full blown distributed applications using SOAP and RPC — you wouldn't (shouldn't) do that with REST API, Graph QL — those are APIs for retrieving state in some representation from a persisted state (hence representational state transfer — REST)

  when you credit/debit a bank account, there is more involvement than just updating a database — your transaction has to clear against hundreds, perhaps thousands of other transactions at the bank — there is an actual [physical] process being carried out and your request to debit or credit you account may be declined at one point in time but approved at a later time… REST API simply involves the transfer of data in some representation (JSON, XML, TXT) — with REST you can cache requests, HTTP verbs matter very much, etc.

• Little more information will be appreciated, though good video

• Super good movie. Thx a lot.

• If it is an Asian saying it, it has to be true.

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

• great video, thanks!

• This is straight forward and clear

• I'm waiting for the day when SOAP becomes the new hotness. Lots of software designs especially on the Frontend seems to go in these cyclical patterns.

• Cool, thanks for explanation!

• Perfect. Thanks!

• Excellent explanation, simple and clear.

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

• Are they TSP or UDP?

• Top-notch explanations

• Thank you so much for sharing your knowledge 🙂

• Thank you for sharing this much of information.

• I like it.

• Thanks always.

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

• Where does SSE fall in ?

• signalR ?

• Complex systems may even have several APIs of different architecture styles

• Sir, I want my server code to access my c++ client, what approach I should use?

• How did you build these beautiful animations??

Comments are closed.