You should drop "(...) and carefully acknowledging them when you are sure data is safely stored in your db (...)" part then, because it means it's not necessary, you don't rely on it.
One-or-more semantics + local deduplication gives one-and-only semantics.
In this case you're optimising local deduplication with strictly monotonic index.
One downside is that you leak internals of other system (partitions).
The other is that it implies serialised processing - you can't process anything in parallel as you have single index threshold that defines what has been and what has yet not been processed.
One-or-more semantics + local deduplication gives one-and-only semantics.
In this case you're optimising local deduplication with strictly monotonic index.
One downside is that you leak internals of other system (partitions).
The other is that it implies serialised processing - you can't process anything in parallel as you have single index threshold that defines what has been and what has yet not been processed.