Request and Response Execution Flow of Commands

Request and Response of Command Execution Flow is discussed

What Components are involved in Command Execution Flow

What Data Passing Data Structures are involved in Command Execution Flow

We selected the Data Access Pattern, by seeing how FAT the Domain Scenario/Feature is. Request Processing Pipeline for different scenarios.

Command is executed in two steps
Request Command 
Response Command

Initial Part of Request Command Execution Flow

Viewè Controllerè Command AS

Passing Data Strcutures for above Operation: 

CommandRequestViewModel è CommandRequestModel

  After reaching the Request, the Orchestration is done in the Command AS

For executing Domain Logic in Domain Model, 

before Saving Data to DB

Command AS è Factories/Domain Services/Entities/VO/Aggregates Roots/ Domain Events
Passing Data Strcutures for above Operation: 

Entities/VO

Response of Domain Logic execution, 

before Saving Data to DB

Command AS ç Factories/Domain Services/Entities/VO/Aggregates Roots/ Domain Events

Passing Data Strcutures for above Operation: 
Entities/VO/TrueFalse/PrimiteDataType/CustomeDataStructure

For Saving Data to the DB, after executing business logic

AS è Repository + UOW Class: 5 Patterns Types è EF è DB

Passing Data Strcutures for above Operation: 
Entities/VO

Showing the response of Command Operation on the UI

View ç Controller ç AS ç Repository + UOW Class: 5 Patterns Types  ç EF Repository ç DB
Passing Data Strcutures for above Operation: 

   GenericCommandResponseModel ç GenericCommandResponseModel ç Entities/VO/TrueFalse/PrimiteDataType/CustomeDataStructure