Drivers, Sessions, Transactions

Sessions are cheap, transactions cost — and managed transactions retry on transient errors.

0/3 done

Overview

Drivers, Sessions, Transactions

Sessions are cheap, transactions cost — and managed transactions retry on transient errors.

Why it matters

The driver gives you sessions (per-thread) and transactions (per-unit-of-work). Read transactions can be routed to followers; write transactions go to the leader.

Make it stick

Use the prompts below to anchor drivers, sessions, transactions to a real graph you own.

›Pick a graph workload you've shipped — where would *drivers, sessions, transactions* have changed the design?
›What's the smallest version of this pattern you could prototype on a real dataset next sprint?
›What is the most likely *misuse* of this idea, and how would you catch it in a model or query review?

Reading in progress · 0 of 3 activities done