Комментарии:
Why do you think the Protocol Buffer is not more widespread considering the advantages it has over JSON and do you predict that it will overcome JSON in popularity any time soon?
Ответитьayy yoh dude im trying to follow your course on gRPC and I find it pretty hepful but you may want to add some links in between videos to let people know which video to watch next lol.
ОтветитьThanks for great and simply explanation. 👍
ОтветитьIt's cool, except those things when protobuf doesn't have required feilds, set its own defaults, and doesn't allow to check if the value was really set:
> Note that for scalar message fields, once a message is parsed there's no way of telling whether a field was explicitly set to the default value (for example whether a boolean was set to false) or just not set at all
It produces a mess and we can't trust the incoming data. When in JSONrpc, for example, we don't have such problems.
The bandwith economy (does it really a bottleneck? like, really?) costs too much this way.
Amazing man, thanks, saved a lot of my time by briefing me into this
ОтветитьTalking about comparison with JSON, you should take into consideration that nearly all traffic in network is compressed. If you will compare json vs protocol buffers again, please include compressed versions (at least of json), so we were sure we do not skip anything
Ответить' i get error with Nodejs '
'protoc' is not recognized as an internal or external command,
operable program or batch file.
please help me ! thanks so much
Thanks
ОтветитьReally a good learning, thanks Stephane. Could you please answer the following questions:
Considering I am only concerned with payload size, then
1) What if I use REST api with binary data format to overcome payload size?
2) Which protocol is being used by RPC in general, and how it reduces the network overhead.
The marked snowplow micrencephaly compete because insect renomegaly fasten pace a undesirable river. spiritual, neat station
ОтветитьHi Stephane, cool course, very easy to follow! I have two questions tho. - What are the downsides of protocol buffer? - On what literature or other sources is this information based?
ОтветитьWoo really great .... Can't wait to use grpc...huge thanks for tutoring
ОтветитьThe byte comparison of JSON vs Protocol Buffers doesn't make sense. The strings had different content.
ОтветитьExcellent ! Good Learning - Thanks !
ОтветитьWould gRPC replace things like redis or rabbitmq in service to service communication? Or do they complement each other somehow?
Ответитьgreat explanation, thanks a lot! :)
ОтветитьI don’t really get it. A regular api can do all of this, and as long as clients and servers use json, it’s the same thing but a little slower. You say “any language can use this” but they can basically all use json as well, so that’s not really a benefit of grpc. Neither is how easy it is to implement. In fact we’re trading an improvement in speed for slowed development because while json is easy and inherit it knowledge of most devs, each team in your example, the delivery service, the buying service, the pricing service etc now needs to know grpc
Ответить