jeudi 16 juin 2016

Onion architecture, persistence and notifications

I am studying Onion Architectures and I have a point.

Onion Architectures aim at isolating the Domain from technological artifacts. Therefore, the guideline is to let the Data Access Layer (DAL) reference the Domain Layer (BL). This way, I should be able to transform entities into storage artifacts. Referencing the BL should probably give me a "snapshot" of my Domain, but without a change-tracking system I will loose all chronological events to know whether inserting, updating, or deleting items in the data-store, to be able to correctly rehydrate the model afterwards.

Do Onion Architectures always need some change-tracking systems, or even something like an event-store ? Am I missing any other pattern ?

Aucun commentaire:

Enregistrer un commentaire