3 ms·
An always empty queue means you could run into problems when traffic increases. I've seen this come up recently, where our queue reader was(well, still is) ove
by 8note 4y ago
An always empty queue means you could run into problems when traffic increases.
I've seen this come up recently, where our queue reader was(well, still is) over scaled, where it could handle 100x the normal queue throughout. When the input rate gets higher though, instead of the queue filling a bit and controlling the traffic, we hammer our dependencies.
I now see a continuously empty queue as a smell. It should be filling and emptying over and over again. Not all the time, but a queue that never fills is a ticking time bomb
- advisedwang 4y agoWhat you're describing (empty queue = unprepared for load) is a code smell, but the solution doesn't have to be "fill the queue sometimes". It could also be: * (Mandatory) Have a back-pressure system. * (Optional, depends on system requirements) have auto-scaling of queue readers. * (Mandatory) Make sure the system is regularly load tested.