When shouldnt you use event-driven architecture?

Hey everyone, I've been thinking about event-driven architectures (EDA) a lot lately. We always hear about how great they are, with all their loose coupling, scalability, and resilience. But what about the other side of things? When does going event-driven actually make things harder than they need to be? Like, for a really simple app that just creates, reads, updates, and deletes stuff, does an EDA just pile on extra work with event brokers and idempotent consumers? And what about systems that absolutely need things in a specific order and want instant consistency? Does EDA just turn into a never-ending fight in those situations? I'd love to hear your stories about the trade-offs you've run into that made you stop and think before using an event-driven setup.