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 the REST API as the default Blazor communication interface

REST is an architecture for distributed systems. It is an easy way to read, edit, or delete data on the server using HTTP calls from the client. Distributed architecture in this context means that multiple servers can handle different parts of the application and communicate through the network. The communication can occur between the browser and the server, but also between multiple servers, where each of them can provide different functionality, such as logging, caching, authentication, and so on.

A REST API (also called a RESTful API) uses URL calls to communicate and is stateless. Thus, every call to the resource (URL) has to have all information to be completed. Each call can be marked as cached, which can lead to performance improvement between the client and the server.

For data manipulation, REST specifies four basic operations: Create, Read, Update, and Delete (CRUD). Each operation has its own...