AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
Using a Load Balancing Processor in Clustered Implementation?
With stateless servers, you can set up a pretty dumb load balancer and every request would get routed essentially to a random instance. Is there any reason to have a bit more of a sharding or pinning of certain workloads in a clustered implementation? I think some of this depends on what you're doing with the collectors. So for example, if you're doing sampling on traces, you wouldn't want your sampling decision being made across.