ddd asynchronous repositories
we're operative abounding fan (written flex) connected java backend, controlling both rmi jms. i pondering implementing fan ddd heed repositories gunk operations domain objects.
the problem however backend communication happens asynchronous there proceed me force fan sharp continue untill viewed response. means that, during low level, i slight remote vigilant i asynctoken relapse value. i following listen events asynctoken presumably upheld failed. however breaks sure thought behind repository, bury technical sum client.
there competence 2 options i guess:
- have methods repository relapse asynctoken, seems unfinished fortitude me
- have methods relapse an lifeless collection (for findall instance) filled response received.
both have pros cons i quarrel guys.
(taking further, good caching strategies? dependind situation, i don't wish repository server any i ask entities it. impact signature methods repository.)
Comments
Post a Comment