gRPC sem mistério: o que é e quando usar no .NET 10
Introdução Imagine um plano de controle que precisa conversar continuamente com agentes instalados em vários hosts. A API envia comandos, cada agente publica heartbeats (sinais periódicos de que continua ativo), informa mudanças no inventário e pode abrir um canal interativo para um terminal. Uma sequência de chamadas HTTP independentes ainda funcionaria para operações pontuais, mas não…
gRPC is not a mystery; it is a remote procedure call framework used for communication between services. In the context of .NET 10, gRPC can be considered for scenarios where services are under the same team's control, need to share generated contracts, or maintain a continuous message flow, particularly bidirectional. It is not a replacement for REST and may not necessarily provide a speed advantage for every application.
Dokpod, for instance, uses REST/OpenAPI for interface operations and SignalR for notifications, with gRPC in the internal channel between the API and agents. This choice addresses a specific system need rather than a one-size-fits-all solution. The first article in a three-part series on APIs and Communication in .NET will provide an introductory guide to GraphQL, while the third will cover SignalR in .NET from hubs to production.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
