Domain-Driven Design in PHP

Modify One Aggregate Per Transaction and Request

Consider the following scenario: you make a request, it gets into your controller, and it intends to update two different Aggregates. Each Aggregate keeps the data consistent within that Aggregate. However, what would happen if the request goes well over the first Aggregate update but suddenly stops (server restarted, reloaded, out of memory, and so on.) and the second Aggregate isn't updated? Is that a data consistency issue? It may be. Let's consider some solutions.

From Vaughn Vernon's Implementing Domain-Driven Design:

In a properly designed Bounded Context modifies only one Aggregate instance per transaction in all cases. What is more, we cannot correctly reason on Aggregate design without ...