Writes to the stream are committed, but writes to the disk are asynchronously synced.
The publish acknowledgement is sent before the sync to the disk is complete.
This could result in data-loss if the server crashes before the sync is completed, however
with an R3+ stream, the replication provides in-flight redundancy to reduce the likelihood of
this occurring with distinct fault domains.
This can significantly increase the publish throughput.
Default: string
All writes are committed and stream data is synced to disk before the publish
acknowledgement is sent.
This is the default mode, and provides the strongest data durability guarantee.
Writes to the stream are committed, but writes to the disk are asynchronously synced. The publish acknowledgement is sent before the sync to the disk is complete. This could result in data-loss if the server crashes before the sync is completed, however with an R3+ stream, the replication provides in-flight redundancy to reduce the likelihood of this occurring with distinct fault domains. This can significantly increase the publish throughput.