Top 9 Most Popular API Protocols
Вставка
- Опубліковано 10 чер 2024
- 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. - Наука та технологія
SOAP is underrated. SOAP is excellent for consultants needing to maximize pain for their clients in order to force their clients to renew outrageously expensive contracts. SOAP is also great for substandard employees striving for that job security we all crave so badly.
Thanks Dem, needed a laugh today 👍🏻 🌟
Thank you for the great video! Over and over again you're talking about the over- and underfetching problem in REST. There are lots of possibilities to solve it staying in the REST frame. JSON:API for example. You can include referenced objects and limit the set of fields for each of them and get precisely what you need in one request.
This channel is literal GOLD!!!
AMAZING. Also for business people relatively easy to understand. Nice.
Great explanation. I have worked with most of these but could not have given such a good explanation
Thank you for this!
Fantastic video
nicely detailed explanations.
can you make videos about test automation tools like Playwright or generally about WebDriver protocol?
Thank you for the great video! If you can tell some video about the front-end about the system design, it will more perfect.
Really a great video after that API Architechture video
Your designs are fascinating and Informative. Could you make a design for Workday functionality and uses?
This is an amazing and concise video! What tool do you use to do the animations?
I have the same question, animation looks sleek , what tool do you use ?
Figma
Webhooks in real world of SaaS integration and interoperability is a disaster; there's no standard for security, error handlng and event processing. Just try supporting 15 SaaS technology platforms and the all have differing webhook models.
That's an easy problem to solve. You just have to select the correct HTTP error code that everyone agrees on.
Webhooks and GraphQL are not protocols. Also, webhooks usually communicate via HTTP methods (POST) or sometimes GraphQL.
Why do you think graphql not a protocol?
Cool
How did you make these cool animations?
Nice Video, Should EDI be here? EDI (Electronic Data Interchange) is not an API, They are different tools for data exchange with distinct technologies and use cases
For all those that overlooked it:
TOOLES USED ARE:
Adobe Illustrator and After Effects
Guess I should make a habit looking at the description
Verdaderamente quedo completamente enamorado
Are your System Interview Books completely separate? Is Volume 1 and 2 separate or are they just 1st and 2nd editions?
lol i was watching your old api video
How the animation in the video was made ?
MQTT = MQ Telemetry Transport, used in IoT
AMQP = Advanced Message Queue Protocol, used in Apache Active MQ
EDI = Electronic Data Interchange, used for data exchange between business systems
EDA = Event-Driven Architecture?
👍👍
1:59 there is typo for webhook
No CORBA/IDL and/or COM? While old, they are still in active use in many enterprises. As are RMI and, certainly, WCF (though i guess that's under SOAP).
you really should've said something about Smithy IDL
Whats the animation tool used here ?
Thy never shared any of the tool which thy used for creating these amazing animated flows.
Check the description@@ManendraG
hey man your content is goildmine can you pls make more clear your voice
There is a buzzing in your mic
1. Rest
2. GraphQL
3. Webhooks
4. SOAP
5. Websocket
6. gRPC
7. MQTT/AMQP/EDI/EDA
8. SSE
Not sure how he got the count 9, also he didnt talk about SSE(which I guess are server sent events)
GraphQL: also, since the schema provides flexibility, it comes with a cost that your RTT now depends on the slowest field in the request. @ByteByteGo Good point about subscriptions, could've highlighted mutations as well.