The Unit of Work Boundary in PHP: One Transaction Per Use Case

A use case that flushes twice can commit half an aggregate. Draw the transaction boundary at the edge and the half-written row stops happening.

venerdì 3 luglio 2026 New tab

1,520 words~7 min read

Book: Decoupled PHP — Clean and Hexagonal Architecture for Applications That Outlive the Framework

Also by me: Thinking in Go (2-book series) — Complete Guide to Go Programming + Hexagonal Architecture in Go

My project: Hermes IDE | GitHub — an IDE for developers who ship with Claude Code and other AI coding tools

Me: xgabriel.com | GitHub

A support ticket lands on your desk. An order exists in the database with a paid status, but no line items. The customer was charged. The warehouse has nothing to pick. You open the row, and it makes no sense: the header wrote, the items did not.

The Unit of Work Boundary in PHP: One Transaction Per Use Case

The Unit of Work Boundary in PHP: One Transaction Per Use Case

Related reading

Symfony Messenger Transports: Building a Transactional Outbox on Top

Hand-Rolled Mappers vs AutoMapper: Keeping the PHP Domain Pure at the Boundary

The src/ Layout for Hexagonal PHP: Layers and Import Rules

PHP 8.4 Asymmetric Visibility: 5 Patterns That Replace Constructors and Setters

# Unit of Work: Managing Database Transactions Like a Pro with Python

singleflight in Go: Collapsing Duplicate Work Under Load

Related reading

Symfony Messenger Transports: Building a Transactional Outbox on Top

Hand-Rolled Mappers vs AutoMapper: Keeping the PHP Domain Pure at the Boundary

The src/ Layout for Hexagonal PHP: Layers and Import Rules

PHP 8.4 Asymmetric Visibility: 5 Patterns That Replace Constructors and Setters

# Unit of Work: Managing Database Transactions Like a Pro with Python

singleflight in Go: Collapsing Duplicate Work Under Load