Book Image

Building Blazor WebAssembly Applications with gRPC

By : Václav Pekárek
5 (1)
Book Image

Building Blazor WebAssembly Applications with gRPC

5 (1)
By: Václav Pekárek

Overview of this book

Building Blazor WebAssembly Applications with gRPC will take you to the next level in your web development career. After working through all the essentials of gRPC, Blazor, and source generators, you will be far from a beginner C# developer and would qualify as a developer with intermediate knowledge of the Blazor ecosystem. After a quick primer on the basics of Blazor technology, REST, gRPC, and source generators, you’ll dive straight into building Blazor WASM applications. You’ll learn about everything from two-way bindings and Razor syntax to project setup. The practical emphasis continues throughout the book as you steam through creating data repositories, working with REST, and building and registering gRPC services. The chapters also cover how to manage source generators, C# and debugging best practices, and more. There is no shorter path than this book to solidify your gRPC-enabled web development knowledge. By the end of this book, your knowledge of building Blazor applications with one of the most modern and powerful frameworks around will equip you with a highly sought-after skill set that you can leverage in the best way possible.
Table of Contents (10 chapters)

Understanding gRPC and how it is different from REST

gRPC is a way to communicate between services. You can think about it as a kind of API that sends the request to the server and expects some data to be returned. The main difference between a REST API and gRPC is the setup and the way it handles and transports data.

gRPC enables contract-based communication between the client and server. You can imagine this communication to be like a handshake between the client and server over available methods that can be used in future calls. Unlike in a REST API, in gRPC, the client and server share the same configuration, so both ends of the communication have the exact knowledge of the data structure of the transferred objects. The contracts in gRPC are called protocol buffers.

Another big difference between REST and gRPC occurs in terms of communication type. As we learned in the previous section, the REST API is used for communication with JSON or XML data serialization. gRPC, on the...