Hello Matheus,

I'm glad to hear that you like the series!

Transaction control in Hexagonal Architecture is such a complex topic that I could write an entire article about it.

There are different approaches:

* You could make the application core transactional and annotate your services with @Transactional (this has the disadvantage that you bring technological aspects into the core).

* You can manage the transactions at the repository level (like I did).

* You can group your entities into aggregates according to Domain-Driven Design and store and load entire aggregates transactionally at the repository level.

* According to Domain-Driven Design, you could put application services on top of the domain services to manage the transactions.

* And more...

The Hexagonal Architecture is not prescriptive in this regard.

I recommend that you experiment with different variants and analyse which is best suited to your application.

Best wishes,
Sven

How could the code be changed to accomplish that?

Apart from this question, everything that I've read up to this point is super informative. Thanks for your great work!