On: Twirp: A new RPC framework for Go

[justinko]

We had to stick to layer 4/TCP via an ELB (as opposed to an ALB).

[Xorlev → justinko]

gRPC connections are persistent, so a single client will always talk to a single backend in that configuration. It's fine if you have lots of clients but can easily lead to load imbalances.

That's why projects such as Envoy exist. I'd link it, but I'm on mobile.

Keep an eye on it.

[puzzle → Xorlev]

You can use round robin load balancing in gRPC without Envoy.

[tacticus → puzzle]

And it's not difficult to swap it out for a consistent hash balancer or other solution.

[johnbellone → justinko]

You are doing L4 load balancing with the ELB? So you can’t do sticky session management? Is that a problem you run into, if so, how did you handle it?