3 ms·
Why is there not a queue system where a server can pull requests when it's ready to handle one? Why must the work to determine where to send a request go to th
by naikrovek 4y ago
Why is there not a queue system where a server can pull requests when it's ready to handle one?
Why must the work to determine where to send a request go to the load balancer, when you could just pull from a queue and save yourself the trouble of finding the exact right load balancer strategy for your application?
- jmholla 4y agoThe thread up here [0] is talking about that in case you missed it. [0]: https://news.ycombinator.com/item?id=35613454 https://news.ycombinator.com/item?id=35613454
- bityard 4y agoThe short answer is that it's more complicated to engineer and has its own set of trade-offs. With the push-based models shown in the article, everything works regular HTTP(S), no fancy routing is needed, and the LB needs to keep very little state to do its job.
- naikrovek 4y agoseems like a request could be pulled from a queue with HTTPS easily enough. and if I am misunderstanding what you're saying, I don't understand why a purely request-driven path is so vital; it's just a way to me ve data around. seems like the queue could accept the request, keep the https connection open, wait for a response from whatever server accepts the request, and pass the response to the client upon receipt just fine. I dunno. web stuff is poorly done imo. poorly designed.