A cider-press co-op must reject inserts when a batch id already exists, while a later nightly sync should insert-or-replace the same items. Which Cosmos SDK pair matches those rules?
Select an answer to reveal the explanation.
Short Explanation
First rule is a bouncer—Create fails if the batch id’s already inside. Nightly sync is a librarian—Upsert puts the book on the shelf whether it was new or a replacement.
Full Explanation
Create-item APIs fail when an item with the same id already exists in the partition, enforcing uniqueness on insert. Upsert inserts or replaces, fitting reconciliation sync jobs. Patch, read, and query do not encode those two write semantics. Distinguishing create versus upsert is the targeted Cosmos SDK behavior.