Introduction To gRPC

[@topunixfan5501]

Thank you so much! Last May I redefined my goals to become a .NET Developer. Probably something very unusual for a 64 year old, but it was that long it took me to realize that was what I really wanted to accomplish. I'm learning C# .NET MAUI using the Visual Studio for Mac 2022 IDE. I'm orienting my learning by developing an App that requires speech recognition. After researching and experimentation I came to the conclusion that I should use the Google streaming Speech-to-Text in its asynchronous processing modality. I know I have to use gRPC, Protobuf, Google.Cloud.Speech.V1, and that my C# business logic has to be multi-thread. That is a lot to handle simultaneously for a newbie like me. Therefore, your presentation has been extremely helpful. Right now all modules of my app are ready and functional. I only have to make speech recognition work. But is has been much more difficult to me than any other of the modules so far. To the point that I'm considering hiring someone to help me with this module. But I'm giving it a last try before hiring someone. Thanks again ❤. Subscribed!

[@itsnotjustcode2255]

Great presentation. This got me interested in gRPC and learned a lot along the way. Whenever I watch your videos, this one included, I keep thinking "this is so much better than any conference speaker talk". This direct presentation to the viewer and direct to the point style suits you quite well. Thanks.

[@Matlus]

Thank you for your kind words! I am humbled. 🙏

[@alexhall840]

We have just started using gRPC in my workplace, so good timing on the video :)

[@Matlus]

Perfect!

[@s0RR0vv]

Great introduction! Thank you very much!

[@Matlus]

Glad you liked it!

[@blazkowicz666]

What an amazing talk 🙏 Sir could please explain MRCP and Uni MRCP for an IVR chatbot Thank You

[@yogij17]

Thank you so much for all these deep informative videos. I have a request, Can you please shed some light on 1) Parallelism, multi threading, multiprocessing etc. and how to effectively use them in C#. 2) What is Task parallel library and what if use with async await. Thank you in advance. :)

[@Matlus]

Hi Yogesh, I have a blog article on the subject or Parallel programming, multi-threading in the Task Parallel library here: www.matlus.com/data-parallel-parallel-programming-in-net/ It's an in-depth article, primarily because the subject is quite complex. I don't think I'll make a video on it, only because it will be way too long and too complicated. Having it in article/blog form allows folks to go at their own pace and also navigate anywhere they choose.

[@yogij17]

@@Matlus Thank you for the link.

[@gajarubanjeyakumar7226]

U r a great teacher. Can you also talk abt the JSON-RPC protocol?

[@Matlus]

Thank you for your kind words Jeyakumar! JSON-RPC is more like XML-RPC. So it's not related to gRPC. Besides, gRPC is the way to go if you need RPC. I don't think I'll make a video on JSON-RPC or XML-RPC, I'm afraid.

[@gajarubanjeyakumar7226]

@@Matlus can i ask why your channel is not monotised? :)

[@Matlus]

@@gajarubanjeyakumar7226 Just haven't got around to turning it on. I do plan to turn it on this year. Thank you for asking.

[@learningwithme6749]

hello, can you make c# playlist so we can watch it one by one thanks keep up great work

[@Matlus]

I have various play lists already. FYI, you can always create your own playlist :)

[@learningwithme6749]

@@Matlus i meant c# one there is no playlist i think so but thanks for attention anyway

[@nikhilramabhadra6052]

You said that quic uses UDP which is connection less. As there is no guarantee of delivery, and ordering of datagrams; how does it even work? In case of video or audio transmission a few dropped packets are tolerable.

[@Matlus]

Good question indeed Nikhil. I can't really say it guarantees delivery and order, I'm guessing it a hybrid of sorts between UDP and TCP.

[@hansrudolf5849]

Hey Shiv, out of curiosity - what's your opinion on GraphQL instead of REST?

[@Matlus]

Hi Hans, I don't believe it's an either or thing. They serve different purposes. However I do believe gRPC replicates how and what we use methods for (which is everything we do) while making it possible to have them execute on a remote machine. They can all do that, but gRPC is intended for it. I think REST and GraphQL stipulate too many Should and Shouldn't doctrines that renders them not "correct" for certain use cases. gRPC on the other hand says "Remote Procedure Call". No stipulations other than that.

[@hansrudolf5849]

@@Matlus Thanks for your quick response - always interesting to hear your thoughts.