gaspersic/java-design-patterns
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
java-design-patterns/cqrs
History
Narendra Pathai 2aa9e78ddd
Minor refactorings and code style changes (#807) 
* Made minor changes in some patterns such as removed throws clause where not needed, changed incorrect order of arguments in assertEquals

* Minor refactorings and code style changes. 1) Removed several use of raw types 2) Removed unnecessary throws clauses 3) Used lambda expressions wherever applicable 4) Used apt assertion methods for readability 5) Use of try with resources wherever applicable 6) Corrected incorrect order of assertXXX arguments

* Removed unused import from Promise

* Addressed review comments

* Addressed checkstyle issue
2018-10-23 13:45:41 +05:30
..
etc
#190 Remove urm plugin
2017-11-28 20:55:52 +02:00
src
Minor refactorings and code style changes (#807)
2018-10-23 13:45:41 +05:30
pom.xml
Set version for next development iteration
2018-09-30 21:05:57 +03:00
README.md
#190 Remove pumlids from readmes
2017-11-28 21:28:53 +02:00

README.md

layout, title, folder, permalink, categories, tags
layout title folder permalink categories tags
pattern CQRS cqrs /patterns/cqrs/ Architectural
Java
Difficulty-Intermediate

Intent

CQRS Command Query Responsibility Segregation - Separate the query side from the command side.

alt text

Applicability

Use the CQRS pattern when

  • you want to scale the queries and commands independently.
  • you want to use different data models for queries and commands. Useful when dealing with complex domains.
  • you want to use architectures like event sourcing or task based UI.

Credits