Command-Query Responsibility Segregation (CQRS)

Commands insert, update, delete Queries select Commands and queries should be separated. This helps to increase scalability on the database.

Why CQRS Queries Collaboration - multiple actors using or modifying the same set of data. Staleness - once data has been shown to a user, that same data may have been changed by another actor. The additional data store can be a bit out of sync with the master database. This can be structured just like the ViewModel and no need to transform objects.

Command-Query Responsibility Segregation (CQRS)

Query Data Storage Does not have to be a relational database.

Scaling Queries If the data being served does not need to 100% up to date we can easily add more store instances without worrying about that they contain the exact same data. Persistence for Command Processing Service Layers Each command is independent, so we don't should allow the objects which handle them to depend on each other. Dependencies are things which should be avoided, unless there is a good reason for them. We can serialized the domain entity and put it into a single column and had another column containing the ID, akin to the key-value storage available from various cloud providers.

Command-Query Responsibility Segregation (CQRS)

Commands and Validation Clients send commands to the server and it does not return errors to the client, but rather notifying the user of the outcome. Validation is different from business rules in that it states a context-independent fact about a command.

Commands and Autonomy Commands don't need to be processed immediately, they can be queued. Shouldn't need to access the query store to process commands, any state that is needed should be managed by the autonomous component.

Failure messages due to the database being down or hitting a deadlock should not be returned to the client, we can just rollback and try again by processing all messages in the queue. Each command could be processed by a different AC, each with its own queue.

Command-Query Responsibility Segregation (CQRS)

Application without CQRS CQRS application

Objectives
General Automate the development of E-Commerce applications for Cloud Computing Specific objectives Describe the features and functionality that have e-commerce applications. Analyze components of e-commerce applications can be transformed using patterns for Cloud Computing. Develop a product line for deployment of application E-Commerce for Cloud Computing. Reduce the time to development and deploy in E-commerce applications for Cloud Computing.