3 ms·
That sounds like instructions for turning a cheap, easy to diagnose problem into a very expensive, harder to diagnose problem. Not to mention the second-order
by kqr 6y ago
That sounds like instructions for turning a cheap, easy to diagnose problem into a very expensive, harder to diagnose problem.
Not to mention the second-order effects: if you pretend to drop exactly 0 % of messages, then people will build things that depend on that condition. When the unexpected happens and that condition is violated, bad becomes worse.
By deliberately designing in the option of dropping a reasonable amount of messages, you're creating a more robust system. (As well as a perfect point for a circuit breaker in an emergency.)
Other than in some very specific domains, dropping messages is not a big deal and the design implications of allowing that are far preferable to designing for a fantasy world in which nothing goes wrong ever.
- Joker_vD 6y agoWhile I agree with you, I think the parent's advice of "autoscale your consumers" is also a good advice, if interpreted in certain sense: that is, when you see that your queues start approaching the uncomfortable sizes, start dropping your clients. When they try to reconnect, they will probably get routed to a different, less busy node.
- cassianoleal 6y agoI would absolutely not want to lose log messages. I'd rather have my queue grow infinitely until I solve the ingestion issues than lose messages, _especially_ but not exclusively audit logs. I don't think logging is _some very specific domain_ but I will concede that this might be due to my own biases because of my role.