Message Queues: Balancing Durability and Speed

Hey everyone, I'm working on a system that really depends on a message queue to keep services separate. We're trying to figure out whether to go for strong durability guarantees, like saving messages to disk before saying we got them, or if we should aim for lower latency, where we'd confirm receipt right after putting them in the queue and just use in-memory replication. What's your experience been balancing these two? Have you ever picked one over the other, and what happened because of it? Any specific ways or setups you'd suggest for different situations?