On Wed, Apr 28, 2021 at 12:57 AM Piotr Morgwai Kotarbinski <
morg...@gmail.com> wrote:
> I was surprised actually, because I thought parallel request message
> processing was a common use-case, both for gRPC and websockets
>
Yeah, we call those "RPCs." They can scale very wide horizontally.
(for
to fulfill the void left by my previous message ;-) here is
ConcurrentRequestObserver which eases up developing bi-di streaming methods
that dispatch work to other threads but don't need to preserve order of
responses:
https://github.com/morgwai/grpc-utils/blob/master/src/main/java/pl/morgwai
Hi Sunandan. For unit tests, it's first worth trying to test your business
logic in isolation from gRPC. For integration tests, you could run your
service and exercise it with test clients (your CI environment may be
opinionated on how to automate that). We also have a doc that offers one
sugge
I'm building out a series of ProtoBuf definitions for a .NetCore gRPC
application.
I'm using the Orchestrator pattern as I will be creating a series of
microservices.
I am running into issues with my proto definitions throwing compiler errors
as being "undefined."
The definitions are in several
I am quite new to gRPC but I wish to use it in my current application.
I am building the Backend Server in NodeJS
I have created my Service Definition file as below:
```syntax = "proto3";
package location;
import "protos/auth.proto";
service LocationManager{
rpc updateLocation(LocationUpd
