architecture - Database Transactions in Application Services as defined by Domain-Driven Design -

architecture - Database Transactions in Application Services as defined by Domain-Driven Design -

in book "implementing domain-driven design" vaughn vernon said on page 120

application services reside in application layer. [...]. may command persistence transactions [...]".

now, controller in mvc application application service, right? if yes, mean controller can commit or roll database transaction (directly or indirectly, through mecanism controller can manage)?

you can view controllers application services, in simple applications, might improve thought have dedicated objects these services because :

controller ui concept. might want alter or add together ui layer , still maintain applicative scenarios intact without rewriting them.

orchestrating calls repositories, domain entities , services plus carrying out applicative transactions might much responsibility controller in charge of dealing view info , view navigation. see fat controller antipattern.

design-patterns architecture domain-driven-design