3 ms·
One option is a reversal: Make the worker request a request. Slow, unavailable or failed workers will in effect automatically back off.
by vidarh 8y ago
One option is a reversal: Make the worker request a request. Slow, unavailable or failed workers will in effect automatically back off.
- jashmatthews 8y agoPhusion Passenger has some intelligent routing to balance requests so you don't end up with one process idle and one process serving two requests using 2 threads.
- vidarh 8y agoLots of systems do, but that's requiring lots of logic in the load balancer. Reversal makes this an emergent property of the system.
- tybit 8y agoI’ve been wondering whether this approach would be viable for a while now. Are there any systems that do this? I know solo’s Gloo reverses the flow using NATS but that’s all I’ve seen use this approach.
- vidarh 8y agoI'm not sure. Mongrel2 uses ZeroMQ to talk to the backends to get it automatic handling of disconnecting backends, but I'm not sure if it's actually waiting for the backends to be ready before sending the next request.