Wrap all Application Layer class/method invocations within a UoW

[subhashb]

Application layer elements, like Application Services, Command Handlers, and Event Handlers, are the primary mechanisms that interact with the persistence store. They fetch repositories associated with aggregates, load aggregates from the database when necessary, and add the changed repository objects back into the store.

It is advantageous to wrap the methods in this layer to run within a UnitOfWork(UoW). While the established guideline is to restrict all state changes to one single aggregate per change, a UoW further ensures that transactional integrity is preserved. It also ensures all events generated at the domain layer are published/dispatched only after a successful commit.

We can accomplish this by wrapping classes/functions as they are registered with the domain:

def decorator(f):
    def wrapped(*args, **kwargs):
        with UnitOfWork():
            result = f(*args, **kwargs)

        return result

    return wrapped