Event-Driven Architecture vs Idempotency

A software architecture pattern where trading systems respond to and process discrete events—price updates, order fills, market signals—asynchronously rather than polling for changes, enabling low-latency decision-making and flexible component communication.

A software design property where performing an operation multiple times produces the same result as performing it once—critical for order execution ensuring that order retries, network duplicates, or system restarts never result in multiple unintended trades from a single order request.