Thoery coding: UI -> people Read and think -> people Do, action ... something -> UI push Command(s) -> Command Handle -> Build Object Domain by Events using Repository -> Domain call action(s) do business -> Repository store Events into EventSourcing Db -> Fire Event -> Event Handle write to Database Read -> Thin Query Facade from Db read -> UI ...
I just do like that: Each command's type will have own queue to store and own thread to execution. Thread will create automaticlly by type of command. Plz look at the code bellow But I wonder that, how many Thread should be create in an application ( for window services, desktop application, web application hosted on IIS) Could some one help me to answer this question?
E-commerce solution develop base on Cqrs, Event sourcing Provide basic code to developer can extend and continue develop We will training and transfer all source code and knowledge
Cms, Ecommerce solution develop base on Cqrs, Event sourcing. Provide basic code to developer can extend and continue develop. We will training and transfer all source code and knowledge.
Cms solution develop base on Cqrs, Event sourcing. Provide basic code to developer can extend and continue develop. We will training and transfer all source code and knowledge.
wating ...