couchbase-transactionslisted

Design and implement Couchbase distributed ACID transactions across multiple documents. Use whenever the user asks about transactions, multi-document atomicity, ACID, transaction library, TransactionAttemptContext, commit, rollback, transaction retry, Active Transaction Records (ATRs), transaction expiry, transaction lost write, transaction conflict, transaction performance, cb_transaction_run, or 'how do I atomically update multiple documents.' Distinct from couchbase-app-integration (which covers single-document KV ops, subdocument ops, and has a brief transactions overview) — this skill is for users who need the full depth: designing around transactions, understanding the two-phase commit mechanics, debugging failures, and tuning performance. Use proactively when the user has a use case requiring consistency across multiple documents.
celticht32/Couchbase-Skills-for-Claude.ai · ★ 1 · AI & Automation · score 75

Install: claude install-skill celticht32/Couchbase-Skills-for-Claude.ai

# Couchbase Distributed Transactions A skill for *designing and implementing* multi-document ACID transactions in Couchbase. Goes deeper than the overview in `couchbase-app-integration/references/transactions-app-side.md`. Distinct from: - `couchbase-app-integration` — general SDK patterns; has a transactions overview but not the depth needed for production transaction design - `couchbase-mcp` — the `cb_transaction_run` tool for running transactions via the MCP server ## When this skill applies - "How do I atomically update multiple documents?" - "How do transactions work under the hood?" - "My transaction is retrying — why?" - "How do I handle a transaction conflict?" - "What happens if the client crashes mid-transaction?" - "Transactions are slow — how do I tune them?" - "What are ATRs and why does my bucket have them?" - "How do I model data to minimize transaction use?" ## Pick the right reference | Question | Read | |---|---| | "When should I use transactions vs single-doc ops vs subdoc?" | `references/when-to-use.md` | | "How do they work? ATRs, two-phase commit, retry, expiry" | `references/mechanics.md` | | "Code patterns — Python, Java, Node; error handling; retry logic" | `references/patterns.md` | ## Core principle: try to design around transactions Transactions in Couchbase are 3-5× slower than equivalent KV operations and add retry complexity. Before reaching for a transaction, ask: can this be modeled as a single-document update? Often the answer is yes.