RoundRobin
Cycles through a fixed set of consumers/servers/tasks one at a time, giving each an equal, predictable share — the default load-balancing algorithm.
Why we need this / what value this brings
Simple and fair when all servers/consumers have equal capacity and requests cost roughly the same to handle.
When to use this
Default load-balancing algorithm for a fleet of identical-capacity instances handling similarly-sized requests.
How to use or implement this
Most load balancers (including cloud-managed ones) default to round robin — only override it once instance capacity or request cost becomes uneven.
Research questions
- Is round robin the right load-balancing algorithm once Localz has more than one backend instance, or would least-connections fit better under uneven request cost?
Empty folder — drop notes, links, and findings here as you research.