100% agreed. Often limits need to be addressed at the product level. At some point at my $work we started pushing hard enough back at product to say that we'r

100% agreed. Often limits need to be addressed at the product level. At some point at my $work we started pushing hard enough back at product to say that we're placing a hard limit on every entity. What the limit is can be negotiated, re-evaluated, and changed -- but changes to it need to be intentional and done with consideration to operational impact. My personal pet peeve is when i'm dealing with a client library that doesn't expose some sort of timeout. I'd also add unbounded queues to the list above as a subtle place where the lack of a limit can really cause production issues. Everything may look like it's working fine until you realize that you've got a 4gb process with a giant buffer that'll take forever to drain.