ORDERS.*in the Stream even though there are many types of order related messages. We'll show how you can selectively consume subsets of messages later. Relatively speaking the Stream is the most resource consuming component so being able to combine related data in this manner is important to consider.
ORDERS.*but we could also consume
SHIPPING.stateinto the same Stream should that make sense (not shown here).
Nats-Msg-Idheader and a sliding window within which to track duplicate messages. See the Message Deduplication section.