Home/ Questions/Q 7979791
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T09:52:11+00:00

I am currently in the process of developing a a rather big web application

  • 0

I am currently in the process of developing a a rather big web application and is using domain driven design.

I have currently run into some trouble with tracking changes to my Product entity. The thing is, products are constructed partly from data in SQL Azure, partly from data in Azure Table Storage. If certain properties are changed, I will need to persist to both, other changes only to one.

As a result I can not use NHibernate or Entity Framework for tracking changes. For instance the Price argument on the

    public void AddPrice(Price price)

method on the Product entity must be persisted to SQL Azure, calculations on a range of prices will take place and the result will be saved to Azure Table Storage.

How would you solve this?

Thoughts:

1) I thought about implementing my own change tracker based on Castle.DynamicProxy, but that seems rather tedious.

2) Implement events internally in the domain entities. This is not a good thing.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Scattering one entity across several persistent stores might not be a good idea. To be more precise, it might mean that it’s not one and the same entity and could be split up in smaller, more accurately designed parts instead.

    calculations on a range of prices will take place

    Are you sure these calculations affect the Product entity and should be handled by the same NHibernate/EF session used in the Product repository ? Since they have to be stored elsewhere, don’t they make up a first class notion in the ubiquitous language, resulting in a separate entity with a persistence logic of its own ?

    See http://ayende.com/blog/153699/ask-ayende-repository-for-abstracting-multiple-data-sources

    • 0