Thread Confinement and Ownership¶

If data is only accessed by a single thread, no synchronization is needed. Thread confinement is an architectural strategy where each piece of mutable state has exactly one owning thread. Data can be transferred between owners, but never shared simultaneously.

Tension Addressed¶

Safety vs. Liveness, Simplicity vs. Scalability

Recognizable As¶

Thread-local storage, single-threaded event loops, hand-off patterns where ownership transfers explicitly, UI frameworks where only the UI thread can touch UI state.

Canonical Sources¶

Goetz, "Java Concurrency in Practice" (2006); Rust ownership model (language-level enforcement)

Transfers To¶

UI programming, database connection handling, any resource lifecycle management