Event-carried state transfer pattern communicates an event with some coupling and networking tradeoffs.

Same intent as event notification, but this design attempts to reduce the need for consumers to follow up for more information by providing a best guess at what is needed up front. This couples at the event production interface rather than other queryable interfaces. It also reduces latency (reduces need for post-event queries) while adding lots of potentially unnecessary network load.rF1 This style is common in CRUD-centric designs which typically couple clients to producers‘ underlying implementations.rC6


  1. Derek Comartin, “Event-Driven Architecture Lost Its Way,” March 7, 2024, https://codeopinion.com/event-driven-architecture-lost-its-way/. (See notes.)

  2. Martin Fowler, “What Do You Mean by ‘Event-Driven’?,” martinfowler.com, 2017, https://martinfowler.com/articles/201701-event-driven.html. (See notes.)