.NET gRPC - deep dive

.NET gRPC - Deep Dive
With an increasing need for scalability and performance dictated by the modern web, it becomes harder and harder to choose an API paradigm that is suitable for service-to-service communication.

While the classical models still work and have their own merits, some of them rely heavily on documentation, extensive coordination between teams or code-sharing. We use shared libraries, and over time our projects become intertwined with dependencies. In these cases, we need something to untangle those and reduce coupling. Welcome gRPC.

gRPC has been around for a while and .NET Core 3.0 welcomes it as a first-class citizen. It is contract-based, performant - with smaller response/request bodies, perfect for polyglot environments and supports different models – from client-server to bi-directional streaming out of the box.
If we sprinkle some client-side load balancing and the ability of exposing a gRPC service also as a HTTP API we might the perfect point-to-point communication mechanism.
In this session, we will deep-dive in how to use gRPC, configure client-side load balancing and gRPC transcoding to streamline communication.

-About the Speaker
Irina Dominte (Scurtu)

Microsoft MVP for Developer Technologies, Software Architect and Microsoft Certified Trainer, always in a quest for latest trends and best practices in architecture, .NET and the world around it.

Irina has more than 1000 hours of delivered trainings, workshops, and presentations, being passionate about .NET and the world around it.

-
Links

-
The Video

-
dotnetsheff

dotnetsheff is a monthly user group focused on software development, particularly in the .NET ecosystem. We welcome people with interests in software development of all ages and levels of experience

[_miranHorvat]

Yeah, funky and faster. That's it. How many developers do realy need this performance gain? Don't get me wrong, it's great. I don't need it. But what I do need is the Decimal type! Back in the days I just added asmx files with methods to my monolith and it was done. Wsdl was autogenerated. Consuming a wsdl is a gem - basicaly a single click and you have your strongly typed proxy classes. Then came wcf along. What did I gain with wcf? Nothing. More work for the same result was the result. And then, I still don't understand the hype, came rest. That was realy stupid. OK, bear in mind, I'm a MS-VS-.NET guy. And now, Ladies and Gentleman, gRPC. The asmx aproach was almost a perfect solution.