Create domain entities for `read-write-pi` module
Problem
For the implementation of Payment Initiation API Specification we should have domain entities.
Solution
Using a UML diagram from the specification create domain entities in the domain
sub-package of read-write-pi
module.
Decisions
Domain
sub-package in read-write-pi
module should be created and filled with every subsection of the data model.
Alternatives
- Create separate DTO and persistence entities with mappers between them - gives unnecessary overhead.
- Do not use java for schema configuration - would give more requirements for developers in terms of skills and knowledge without pros.
Concerns
- Changes in Specification would require migration of data.
Assumptions
- We would use domain entities for both - persistence and representation.
Risks
- Changes in the specification would require additional actions [2;6]