Event-driven systems decouple services by having one service publish facts (events) rather than calling multiple services directly, reducing latency and coupling but introducing eventual consistency challenges. A payment capture example shows how event-driven architecture improves availability and deployment autonomy compared to request-driven systems.