gRPC Explained

preview_player
Показать описание


#neetcode #leetcode #python
Рекомендации по теме
Комментарии
Автор

mostly good info, but REST does not have to be JSON. it's a pattern for the idempotent exchange of information. you can actually write REST style api endpoints using protobuf or xml too, or really any representation of data that you decide on. Binary formats for data exchange have been around for a very long time. gRPC reinvents the wheel for a lot of companies that have been doing REST style calls for years. where gRPC can be considered good is it defines a format for constructing data transfer object definitions (classes) in the language of your choice as long as someone has written a formatter for your language

conundrumu
Автор

Please continue making more of these it helps me a lot

lilchuwwy
Автор

All these API "patterns" are just derivatives/extensions of PROACTOR and REACTOR pattern. There are only 2 patterns just implemented slightly differently...

Rasmanit
Автор

REST APIs must be driven by hypertext. Those endpoints using json can, at best, be called Rest-like.

Niquito-zzdb
Автор

Continue making these short and easily digestible content. Helps a lot!

rusirumunasingha
Автор

Yeah google does everything in protos. It’s interesting and they argue necessary for their scale. But ehh probably just cause they wanted to be different.

bluesquare
Автор

Funny how we're now going back 25 years, when having binary protocols was common.

waperboy
Автор

gRPC folks when they realise SOAP architecture had this for years and Google just made an optimized data format to support it

k_gold
Автор

gRPC web for browser, also using proto buffer?

yuliangjin