ACID describes four transaction properties—atomicity, consistency, isolation, and durability—that support reliable database behavior. A database management system provides these properties as part of its support for structured, secure data management. section 4.1
In an ASP.NET Core web API, a DbContext commonly represents one unit of work within a single HTTP request/response lifecycle. Keeping the database operations for that business transaction together helps preserve ACID properties and coordinate concurrency-related changes. section 4.3.4
Board-game API transaction flow
A GET request can use an injected DbContext to read board games, map the resulting entities to DTOs, return JSON, and then dispose the context. A PUT request can use the same unit-of-work pattern for a mechanics-wide rename, such as replacing “war” with “conflict.” section 4.3.4
builder.Services.AddDbContext<ApplicationDbContext>(options =>
options.UseSqlServer(
builder.Configuration.GetConnectionString("DefaultConnection"))
);
Configure the application DbContext with dependency injection and a SQL Server provider before using it for request-scoped database work. section 4.3.4
