Skip to content

Parallel write use case

moulliet edited this page Mar 4, 2016 · 3 revisions

For cases where read ordering are not required to be exactly the same as write order (otherwise see Sequential Write Use Case), the requirement is that read order should be consistent. That is, once a consumer reads data from the channel, subsequent reads of the same items at a later date will be in the same order.

To do this, there needs to be a lag from now for the latest items in a channel. By default, this lag is five seconds.

Clone this wiki locally