3 ms·
I think that is the wrong conclusion. You still have the problem of having to design a system where the dynos communicate their queues to the second layer of t
by jcampbell1 14y ago
I think that is the wrong conclusion. You still have the problem of having to design a system where the dynos communicate their queues to the second layer of the routing mesh.
The solution is to have dynos large enough that you can run 8+ workers and let the operating system do all the complex scheduling.
- thu 14y ago> and let the operating system do all the complex scheduling. So Heroku could spawn workers with a $FD environment variable instead of $PORT and the "complex scheduling" done by the OS _is_ the second routing layer. But really, they could still do a second level routing even outside a single OS as the scale of the distribution is much smaller, so having the routing mesh be aware of the worker availability seems feasible again.