Why gRPC is Popular #javascript #python #web #coding #programming

Animation tools: Adobe Illustrator and After Effects.

Checkout our bestselling System Design Interview books:

ABOUT US:
Covering topics and trends in large-scale system design, from the authors of the best-selling System Design Interview series.

[Dhtkna]

Ridiculously dense and efficient way to teach. Amazing, thanks

[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-gjdc]

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.

[straightupup]

Remember CORBA? Generate client/server code from CORBA IDL interface definitions, that's essentially gRPC minus transaction propagation you get with CORBA.

[demogyani]

Don't worry in few years we will have gSOAP and gREST😂. This field always goes through full circle.

[charliesumorok]

Besides the format discovery in REST, REST and gRPC can give nearly identical network performance.

[conundrumu]

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.

[supriyochatterjee]

Best teaching of most difficult concepts in the world in the simplest way.

[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

[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

[aurinator]

Surprised Rust's Tonic wasn't listed along with all the other languages.

[SatyamKumar-bwvi]

faster and language-independent, in our Technology (5G & 6G) also we are using gRpc.

[annoorange]

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

[alessiozamboni]

is not really smaller... in terms of size, the library needed is huge and quite complex. You can leverage Protobuf (the serialization used on gRCP) on lighter protocols to have lighter and smaller applications

[blaaaaaaaaaaaaargh]

And slowly we're going back to WCF

[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

[jcdelacruz]

I encountered a significant challenge in handling custom business errors across microservices.

[Nekroido]

People love gRPC because it allows them to build distributed monoliths instead of designing proper scalable event driven microservices

[MasterSergius]

But it doesn't support some datatypes and no custom validation, thus you should write some big wrapper in most cases

[driveDoses]

Till now I thought rest webserices is the latest one. Now companies are switching to new one. Now I need to learn this one too😂