Had to write my reply twice because I'm twitter-illiterate

I agree. Truthfully, I dislike working with the aggregate pattern and have found that the concept is difficult for many teams to grasp collectively. In a couple instances I've chosen to scrap the pattern to favor code that is more verbose, but easier to follow. Largely for the reasons you mentioned.

I've generally felt that the aggregate root more or less *is* a transaction, formalized as an object in code. Mutating multiple aggregate types feels akin to coupling services, and is usually an indication (to me) that I should scrutinize my model. That's my character-limited two cents 🙃

Great effort by the team, very excited for next year, everyone played their... oh sorry, I'll have to finish my comment later, Kirby Smart just called another TO.

The original FFVII is always cheap on steam and is an evergreen classic. If you're looking for something more modern, dive into Octopath Traveler 2!