
transactions
Database transactions, ACID properties, and concurrency control
Database transactions, ACID properties, and concurrency control
Database Transactions Skill
Overview
Understand and implement database transactions with ACID properties and proper concurrency control.
Topics Covered
ACID Properties
- Atomicity
- Consistency
- Isolation
- Durability
- Trade-offs
Isolation Levels
- Read uncommitted
- Read committed
- Repeatable read
- Serializable
- Snapshot isolation
Concurrency
- Locking mechanisms
- Deadlock handling
- Optimistic locking
- MVCC concepts
- Lock monitoring
Transaction Patterns
- Savepoints
- Nested transactions
- Distributed transactions
- Two-phase commit
- Saga pattern
Prerequisites
- SQL fundamentals
- Database concepts
Learning Outcomes
- Implement ACID transactions
- Choose isolation levels
- Handle deadlocks
- Design concurrent systems
You Might Also Like
Related Skills

zig-system-calls
Guides using bun.sys for system calls and file I/O in Zig. Use when implementing file operations instead of std.fs or std.posix.
oven-sh
bun-file-io
Use this when you are working on file operations like reading, writing, scanning, or deleting files. It summarizes the preferred file APIs and patterns used in this repo. It also notes when to use filesystem helpers for directories.
anomalyco
vector-index-tuning
Optimize vector index performance for latency, recall, and memory. Use when tuning HNSW parameters, selecting quantization strategies, or scaling vector search infrastructure.
wshobson
similarity-search-patterns
Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.
wshobson
dbt-transformation-patterns
Master dbt (data build tool) for analytics engineering with model organization, testing, documentation, and incremental strategies. Use when building data transformations, creating data models, or implementing analytics engineering best practices.
wshobson
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
wshobson