| bio | website | ezetop.com |
|---|---|---|
| location | Dublin, Ireland | |
| age | ||
| visits | member for | 1 year, 2 months |
| seen | Jan 2 at 17:41 | |
| stats | profile views | 1 |
My views do not necessarily represent those of my employer.
|
Mar 15 |
comment |
CQRS and cache invalidation (while load balancing) Now I just have to figure out how that maps to dependency injection! (Namely: ICanChange implmentations are per request, but the IObserve<T> impl (the cache invalidator) is long lived) |
|
Mar 15 |
comment |
CQRS and cache invalidation (while load balancing) So I do think that I am in agreement with you: Caching is a decorator on a concrete core impl that reads the data. and I do agree that concept should not pollute the interface. However, I think I need to have a "data changed" event/notification concept modelled in the ICanChange interface. Perhaps it;s just as simple as ICanChange must "inherit" from IObservable<T> (where T is some kind of key class that can identify user/role pairs) |
|
Mar 15 |
comment |
CQRS and cache invalidation (while load balancing) OK. Understood. What would a view look like? Can you point me at any examples or reference material? |
|
Mar 15 |
comment |
CQRS and cache invalidation (while load balancing) Well, the caching is handled by a read-decorator, so in that sence it is an aspect. I think I need an observer that is notified when a write occurs, and that object is responsible for invalidating cache items. I would just like to figure out how to make that a first class concept of the ICanChangeDomainRoles interface... |
|
Mar 15 |
comment |
CQRS and cache invalidation (while load balancing) @Miau: Not sure I understand. I think you are referring to a concept around event-sourcing, which I did not mention. In my app, the cache is the view, so my question becomes how can I update (invalidate) the view (cache) when a write occurs? |
|
Mar 14 |
comment |
CQRS and cache invalidation (while load balancing) I understand that CQRS does not promise instant consistency (delayed writes). But I want the data to be consisted AFTER the write has occurred. That's why I want to invalidate the cache when writes have completed. |
|
Mar 14 |
awarded | Student |
|
Mar 14 |
asked | CQRS and cache invalidation (while load balancing) |