Introduction to gRPC: A general RPC framework that puts mobile and HTTP/2 first Conference by Mete Atamel, Ray Tsang Voxxed Days Luxembourg 2017
КОМЕНТАРІ: 26
@prakharbansal13 роки тому
Really awesome video on this subject.
@patriciasquared3 роки тому
congrats on the live demo!
@venkataabhiramsrivatsavape2299 місяців тому
Energetic Seminar for gRPC.
@90hijackedРік тому
These guys are so passive aggressive towards each other this clip could pass as standup comedy, love it
@MegaMurcelagoРік тому
gosh im in love with that turbofan laptop picture
@truthseepeaking2 роки тому
These guys were having too much fun on the stage
@joshuam60133 роки тому
this was so cool!
@nooruddinraotiwala490Рік тому
hey amazing work explaining so simplifiedly and funny way😃🙌....!!!!
@patle82292 роки тому
could you share the demo code ? 😁
@BunmJyoРік тому
要说用得最舒服的grpc server构建,还得是微软的一套东西
@cppdev27295 місяців тому
don't see how this was more simpler than cobra
@sirAvdulРік тому
One thing, does the client needs the protoc file too? If yes, does the server and the client share/use the same protoc file?
@madhudson1Рік тому
They share the same protobuff file, yes
@abhishekdk504011 місяців тому
It's an API contract which both client and server abide by
@javadborhani78385 років тому
it's quite funny how well java programmers typing confidently and c# developers just copy and paste or watch and type. it even happens in Microsoft build or their events. anyway I'm a c# developer
@obinnaokafor62524 роки тому
Funny comment
@pwilll2 роки тому
40k views and 15 comments? Who says developers aren't social? Because they're correct lmao
@utkarshdixit96752 роки тому
did you get raise, after demo ?
@vishvajeet76252 роки тому
lol
@markcuello5Рік тому
HELP
@dgusev2 роки тому
Putting RPC over HTTP is inefficient and ugly. HTTP is an application level and RPC should travel via transport level, that would be the good design. Why do we require the HTTP in this case? We can easily define multiple streams inside single TCP or TLS connection if needed, other protocols also could be an option, SCTP for ex. You talk a lot about efficiency here, but using HTTP as a transport is really an inefficient part. A also wonder why people forget and do not use good things invented and developed, like SCTP.
@sidekick3ridaМісяць тому
Java is so verbose and ugly and disgusting.
@kartikchauhan54984 роки тому
If gRPC is this much fast then use it in damn chrome. It consumes up my system's whole memory.
@amelemara46154 роки тому
grpc is a messaging protocol over the network between a website (client) and its servers.Chrome just renders what a website tells it to. The use of gPRC depends on what websites you use and if they use it. So like going to netflix you might be using grpc but going to facebook they might be talking over a different protocol like REST.
@mehmetesen93854 роки тому
grpc has no bussiness with your chrome, also chrome is very good at memory handling, you should buy ram.