Eloquent Events vs Domain Events: Why the Framework Hook Isn't Enough

Eloquent's saved hook fires on persistence, not on business intent. Here's why that gap ships bugs, and how to raise real domain events.

giovedì 2 luglio 2026 New tab

1,628 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

You wire a listener to Eloquent's saved event on the Order model. When an order is saved, send the confirmation email. It works in the demo. Then a support ticket lands: a customer got two confirmation emails for one purchase, and another got a refund receipt for an order that was never refunded.

Eloquent Events vs Domain Events: Why the Framework Hook Isn't Enough

Eloquent Events vs Domain Events: Why the Framework Hook Isn't Enough

Related reading

Translate Infrastructure Errors at the Adapter, Not in Your Domain

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

Migrating Laravel to Symfony Without Rewriting Your Domain

Symfony Messenger Transports: Building a Transactional Outbox on Top

Event-Driven Architecture: Uncle Explains Like You're Five 👦👨‍🦳

Laravel Nightwatch: First-Party APM and What It Actually Replaces

Related reading

Translate Infrastructure Errors at the Adapter, Not in Your Domain

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

Migrating Laravel to Symfony Without Rewriting Your Domain

Symfony Messenger Transports: Building a Transactional Outbox on Top

Event-Driven Architecture: Uncle Explains Like You're Five 👦👨‍🦳

Laravel Nightwatch: First-Party APM and What It Actually Replaces