Leastconn also have very nice characteristics, that if your app say gets into long GC it will near-immediately stop sending connections there Also the "overrun

Leastconn also have very nice characteristics, that if your app say gets into long GC it will near-immediately stop sending connections there Also the "overrun" of dropped connections shouldn't really happen if * incoming connections are < total capacity * loadbalancer have server limits set properly and doesn't send too many connections for app to stgart dropping * loadbalancer itself is one queuing (as it "knows" the next server that should get the connection) So that part of the description is subtly wrong; you WANT to queue on loadbalancer, not on app servers. The app server should have queue just long enough to feed all the threads but not enough to start dropping anything