As technology, I should support CQRS pattern and event sourcing concerns combined

[olivierlemee]

https://www.notion.so/cybnity/495-d249e159f38a42b4b0d122f33097b0f3

REQ_SCA_4: https://www.notion.so/cybnity/REQ_SCA_4-e587a7c664274a06ab40e44e78a79c00 Apply the event sourcing design (standalone event sourcing, event stores, underlying storage, consistency).

implementation:

• [x] domain event
  • [x] concept
  • [x] unit test
• [x] process manager
  • [x] concept
  • [x] unit test
• [x] command
  • [x] concept
  • [x] unit test
• [x] domain model
  • [x] concept
• [x] persist
  • [x] concept
  • [x] unit test
• [x] publisher
  • [x] concept
  • [x] unit test
• [x] subscriber
  • [x] concept
  • [x] unit test
• [x] event forwarding through messaging middleware
  • [x] concept
  • [x] unit test
• [x] notification log and non complex event message-based notification
  • [x] concept
• [x] event supporting tools and patterns (576) about serializers, immutability, value objects
  • [x] concept
• [x] cqrs
  • [x] (223)
  • [x] events sourcing (235) + event stores (561)
  • [x] read and write models, querying read model
  • [x] commands and command handlers
  • [x] event and event handlers
  • [x] cqrs command validation
  • [x] event versioning
  • [x] messaging considerations (268)
• [x] components documentation

[olivierlemee]

immutable domain event and identification

[olivierlemee]

event store and event sourcing elements coded.

[olivierlemee]

Process manager including publisher/subscriber samples are coded. Unit tests shall be coded:

• [x] unit test regarding store (EventStoreUseCaseTest) need to be finalized to validate the mechanism of subscription/auto-notification
• [x] coding of a datastore example for useraccount and roles + datastore use from ApplicativeRoleAllocationCommandHandler (line 65: found account from identifier) + datastore use from UserAccountCreateCommandHandler (line 68: save created account)
• [x] creation of unit test scenarios using the AccountsManagementServicesImpl model sample with test of command sends with:
  • [x] UserAccountCreateCommand sent generating datastore storage, events on read model (unit test shall listen the received UserAccountCreationCommitted event as integrated handlers/behaviors of components that validate the test)
  • [x] AssignRoleToUserAccountCommand sent generating search/found of user account aggregate, update of his role(s), notification to read model (unit test shall listen the received UserAccountApplicativeRoleAssigned event confirming the test success from the aggregate itself)