api design, when to favor event-driven over request-response. dont you think its a bit of a tough call sometimes?

Hey everyone, I've been giving our API design patterns some thought recently. Most of what we do is request-response, and that's fine for a lot of synchronous stuff. But for tasks that just take time or don't need an instant answer, I'm wondering if we should be using an event-driven architecture with message queues more often. Think about stuff like processing an order or sending out notifications. What makes you decide between those two main ways of doing things? I'm curious to hear what you all have found works well, and if there are any pitfalls I should watch out for.