CQRS

1. What is CQRS?
-based on the Command Query Separation principle
-The CORS stand for Command Query Responsibillity Separ action and is extensional the CQS for objects
-CQRS is not an architecture style, if a antipattern to use
-Command can change the state of the object  but can't return any value
-Query can return value but can't change the state of the object

2. Clean Architecture
-Very similar to other layered architectures like Hexagonal Architectur and Onion Architecture
-Nothing in an inner circle an know anything at all about something in an outer circle
-Entities contains business logic
-The use case layer define the data flow, H?ere we will use the CQRS
-The Interface layer is a bridge between application and external parties like web be owner or mobile application
-the last layer is the framework and libraries

3. Summary
-The CORS is not a silver bullet, and should be use with caution
-The Clean Architecture adds complexity but can prepare the application for the future growth
-Let's be lean, we don't need to go with the state-of-the-art-architecture from the day  one, let's just be ready for it