event
A message stating a fact that already happened, such as order placed, for anyone who cares to react.
In more detail
An event names no handler; any number of consumers may subscribe without the producer knowing. That makes adding consumers easy and makes it hard to know everything that happens next. Facts that others may want again belong on a log.
Related terms
- command message — A message instructing one specific handler to do something, such as charge this card.
- append-only log — A data structure where new entries are only ever added at the end and existing entries are never changed in place.
- publish-subscribe — A messaging pattern where senders publish messages to a named channel and every subscriber listening on that channel receives a copy.
Taught in
- Back Of The Envelope Estimation: Traffic And Throughput — Scalable System Design & Distributed Architecture
- The Storage Decision: Key Value, Search And Blob — Scalable System Design & Distributed Architecture
- Partitioning, Sharding And Hot Keys — Scalable System Design & Distributed Architecture
- Consistency, And The Truth About CAP — Scalable System Design & Distributed Architecture
- Queues, Events And Asynchronous Work — Scalable System Design & Distributed Architecture
- The Difference Between A Queue And A Log — Scalable System Design & Distributed Architecture
- Idempotency, And Exactly Once As A Fiction — Scalable System Design & Distributed Architecture
- Observability As A Design Input — Scalable System Design & Distributed Architecture
- Capacity Planning As A Design Input — Scalable System Design & Distributed Architecture
- Worked Design One: Ticket Booking, Correctness First — Scalable System Design & Distributed Architecture
- Worked Design One: Scaling The Ticket Booking System — Scalable System Design & Distributed Architecture