...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Layers within microservice:
...
- AuthenticationHelper goes to Application layer since only this layer should be responsible for security handling,
- MoneySerializer/MoneyDeserializer goes to Web layer as this layer is responsible for user interface, so for de/serialization from/to JSON)
- RequisitionHelper code should be refactored and find its place in DDD building blocks in Domain layer (some code goes to Entity, some to ValueObjects)
Exception package
This pakage should be removed. We should follow our style guide: Exception classes should go with the classes that throw the exception. If more than one layer use Exception it should be placed with given order: 1. domain; 2: service; 3: web
Validate package
Eventually, we want to get rid of this package. Business logic validations should find place in domain layer, constraint validations should be at database level, all others in application layer.
Open questions:
- Overall: makes sense to align around a typical 3 layer arch: presentation, domain, repository: https://martinfowler.com/bliki/PresentationDomainDataLayering.html
- In infrastructure layer, it really just looks like a repository layer.
- A seperation of "web" and application service makes sense to me
...