The event envelope, and what can be said about one without touching a broker.
An event crossing a process boundary carries more than its payload: which module emitted it, which request caused it, and which tenant it belongs to. The first is for the reader of a log, the second keeps one correlation id across an asynchronous hop the way the RPC adapter does across a synchronous one (BOU-90), and the third is not optional — an event delivered to the wrong tenant is a data leak, not a bug in ordering.
FC/IS: pure. Nothing here connects to anything.
The event envelope, and what can be said about one without touching a broker. An event crossing a process boundary carries more than its payload: which module emitted it, which request caused it, and which tenant it belongs to. The first is for the reader of a log, the second keeps one correlation id across an asynchronous hop the way the RPC adapter does across a synchronous one (BOU-90), and the third is not optional — an event delivered to the wrong tenant is a data leak, not a bug in ordering. FC/IS: pure. Nothing here connects to anything.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |