message queue durability, when is loss okay? dont get me wrong, sometimes you can afford a little data loss, but when?

hey folks, thinking about message queues and their durability guarantees. we often aim for 'at-least-once' delivery, but that implies some possibility of duplicates and requires idempotent consumers. what's your take on scenarios where 'at-most-once' delivery might be acceptable, or even preferable, to reduce complexity? are there specific use cases where a tiny chance of message loss is a worthwhile trade-off for simpler consumer logic or higher throughput