When RESTful architecture isn't enough...

please do not steer development into grpc, I am not smart enough

So basiclly GraphQL, omg

Please... Python

can you make a demo using nodejs ... hehe

"much more secure than running locally" that's where you quit watching the video

u got my sub bro ❤

The browser does not support gRPC which is a bummer

Please do gRPC video using C#

Bruh, I realy made my APIs like this and had no idea it's called RPC 💀

looks like somebody picked up the dropped ... SOAP 🤣
bad joke, i know, but this video triggered some dejavu's for me
good video, as always. thx

Ain't nobody sane writing their OpenAPI docs themselves, attribute configuration for example in C# will produce the correct results automatically and you can automate the endpoint mapping.

can protobuf define form rule?
like input A cannot be greater than 9.

This really seems like the difference between OOP and functional programming to my admittedly pretty naive eyes. I can see where some blending is likely over time.

GRPC on php please :D

How do you make updates to an existing grpc? Wouldnt that require update frontend and backend at the same time so they follow the same contract again?

How can i design my terminal to look as good as yours?

Hey your video was very well produced I like the way you explained it!

if you want the flexibility of rest and graphql, forget grpc. it's not meant to be flexible. Few things to consider: date/time, envoy, and type generators for your web client, you just have to accept the oddity, not disadvantages, just different.

Hey @dreamsofcode, would you please compare gRPC to GraphQL as well?

Can somebody explain on what is meant by the sentence native web support? How is it there for REST but not gRPC? Any example if possible.

I wish this video was with nodejs

Wait... The sponsor is "Acorn"? I know that they are a different company, but the name is similar to that of the company which invented the ARM architecture, Acorn Computers Ltd. . Just reminded me of that.
Nice video, anyways; the animations are great.

gRPC is really good, I love using it. Only downside is that it needs envoy to support web client.

I sometimes find gRPC extremely slow, even when doing the simplest of RPCs

So the Error type does not appear in the contract with the client? 🤔.

Also, is there a way to include more “custom” validation in our contract?, for example in openapi you can put min/max limits, regex and other stuff? (or at least include a message to indicate something)

So we're back 20+ years to SOAP with WSDL and XSD.
This is not a bad thing per se but let's agree this is not an innovation.
Yes, ProtoBuf is pretty efficient compared to the clunky XML messages in SOAP.
And I'm excited about the Subscription capabilities in gRPC. Your videos are well-done and informative, so I'd be grateful for a video on Pub/Sub with gRPC.

On the other hand, in gRPC, we lose the whole hypermedia concept of REST/HATEOAS/HAL.
In well-done RESTful APIs you don't care about IDs and what endpoint to call because the resourse you GET contains hypermedia links with the exact endpoint to call (including the ID). To me, that was a truly remarkable shift in mindset when designing APIs.

In closing, I appreciate this video. It illustates well that RESTful thinking does not fit to all problems, building a calculator being one of them.
Thanks!

lol... "first we need to install a couple of tools..." x17

No thanks.

Great video of grpc. Would love to see an example in nodejs

Could you do a video about gRPC in rust?

gRPC is great for internal server <-> server but I think it falls short everywhere else.

When I worked at Google we had to used gRPC for our apis, the language we used was Java for a microservice

what terminal do you use?

Hey, I know you have said before that you were going to show how you make your animations, I'm really impressed with them! In terms of tooling, you've said before that you use ffmpeg for terminal recording. What do you use for the animations or editing?

please do this in Python and show

There is a major difference between RESTful and RPC-based APIs. By their very nature, every single RESTful operation is atomic. And a good portion of them are guaranteed to be idempotent. This is not at all true with RPC-based APIs.

Additionally, it's very tempting to model an RPC based API as a function call (after all, the word "procedure" is in the name). This is a terrible idea.

Function calls, by their nature, have no built-in latency. The function itself may take some time. But the call takes hardly any time. This is not at all true for RPC calls. Every single call comes with non-trivial (usually at least microseconds, and often milliseconds) latency.

Additionally, function calls are 'reliable'. Oh, your program my die. The function call may not be able to accomplish its task and report a failure. But, your function call isn't going to fail in flight where it seems like maybe it failed, but the call is actually running. This isn't true of an RPC 'call'. And the lack of guarantee of idempotency makes that a huge problem.

So, once you move to an RPC model, the problems you have to solve just became hugely more complex. And the care you have to exercise in crafting your interface is extraordinary. Do not use an RPC API unless you absolutely have to. And when you do, please design it as if you were designing a protocol, not a function call interface. Because that's what you're doing.

It should NOT be called RPC. It makes it sound a lot friendlier than it is, and encourages the wrong mental model in your head.

Also, a calculator is trivially modeled as RESTful.

I unfortunately simply do not see much use of gRPC in my domain of SPAs based business processes. Actions happen on business objects in the SPA, not really through the API. The API is there for validation, persistence and event based process guidance.

it is difficult to set up. too many steps.
now if i were creating some microservices, and i wanted a very performant api client, i would think about grpc for sure. but if im building for a client, i'd stick to rest. grpc and protobuff have great performance boosts. however, everything comes at a price.

hey

Make a video of GRPC in Python , Please

Rust gRPC examples please :)