README
The missing, complete example of Domain-Driven Design enterprise application
Command Query CRUD Responsibility Segregation
Not every piece of software is equally important... Not every piece will decide about company / product success or can cause not reversible negative business consequences like materialise brand risk or money loses. On the other hand scalability or non functional requirements are different for different activities in software.
To accommodate to those differences, separate architectural patterns are applied:
Simple Create Read Update Delete functionality are exposed with leverage of CRUD framework.
Goals of that approach:
- fast initial development,
- fast respond to typical changes (ex. „please add another 2 fields on UI”),
- exposure of high quality API.
Examples in code:
- CRUD-able document ProductDescription
- persistence of document ProductDescriptionEntity
- CRUD exposed as DAO and REST endpoint ProductDescriptionDao
Complex Commands (business processing) expressed in Domain Model which is embedded in hexagonal architecture.