This could lead to a single point of control of at-least-once processing possible, e.g. potentially turning off write-ahead log completely on rocksdb (since kafka writes are primary they serve as a wal) and use a single rodksdb synchronous write to participate in the input-stream-processing work commit.
https://github.com/facebook/rocksdb/wiki/Basic-Operations#asynchronous-writes
This could lead to a single point of control of at-least-once processing possible, e.g. potentially turning off write-ahead log completely on rocksdb (since kafka writes are primary they serve as a wal) and use a single rodksdb synchronous write to participate in the input-stream-processing work commit.