Downsides of CommitAsync() w/o any changes to collection
All the samples usually demonstrate some sort of change to reliable collections with CommitAsync() or rollback in case of a failure. My code is using TryRemoveAsync() , so failure is not a concern (will be retried later). Is there a significant downside to invoking tx.CommitAsync() when no changes to reliable collections where performed? Whenever you open a Transaction and execute commands against a collection, these commands acquire locks in the TStore(Collection) and are recorded to the transaction temporary dictionary(Change tracking) and also to the transaction logs, the replicator then