@straightup7up
Remember CORBA? Generate client/server code from CORBA IDL interface definitions, that's essentially gRPC minus transaction propagation you get with CORBA.
@Mr.Andrew.
Please keep feeding me important system design information across my lazy entertainment feeds! You make me smarter while I attempt to be lazy. Kudos!
@David-gj6dc
I also want to note you don't need to use gRPC to encode your data using protocol buffers. You can still get a lot of the network savings on your REST endpoints by leveraging protocol buffers by itself.
@WhiteDoppler
gRPC is pretty neat, only problem comes when you try to deserialize an empty buffer into a simple data type, which can result in a valid message object from invalid data
@ShortFilmVD
Ah, takes me back to the 90s π a fair few big-name companies in the UK are still running Perl codebases that talk to each other over RPC, never needed replacing
@laughingvampire7555
10 years ago I remember people talking about REST and reminding that "all of this comes in waves, 10 years ago we were talking about CORBA & RPC, now we are talking about REST in the next 10 years we are coming back to CORBA or something similar" and here we are.
@oncedidactic
best quick synopsis on this I've seen. thanks
@conundrum2u
what a lot of people don't realize is because protobuf is a binary format, you have to be very careful how you change your message format and who has access to new message formats in a certain time frame. I'd recommend grpc for high load services that don't change much. versioning becomes necessary.
@AllanSavolainen
I hate it for public APIs, fine for internal ones but classic REST APIs are superior and don't require any libraries to work
@WilliamDye-willdye
*Reduces boilerplate
@robfielding8566
the fact that it forces the use of http2 means that you can't use it in common proxy scenarios. it doesn't fit in well with normal http file handling. from the front-end, you still need to use REST in a lot of cases. some things that are interesting about it have more to do with when you have green-field binary protocols; and don't need to mix well with big files or the front-end.
@moibe182
Awesome short, love your style.
@supriyochatterjee4095
Best teaching of most difficult concepts in the world in the simplest way.
@toetoeag
great explanation π
@εε§εε§
Straight to the point, nice
@demogyani2419
Don't worry in few years we will have gSOAP and gRESTπ. This field always goes through full circle.
@miss-astronomikal-mcmxcvii
Learning gRPC and Protobuf now! Very interesting, I like it :)
@annoorange123
I cringe every time people mention REST in this discussion. Not once has JSON over HTTP mentioned in Fielding's dissertation. REST is agnostic to underlying protocols
@charliesumorok6765
Besides the format discovery in REST, REST and gRPC can give nearly identical network performance.
@Dht1kna