Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
37 tasks done
olivierlemee opened this issue Nov 25, 2022 · 3 comments
Open
37 tasks done
Assignees
Labels
line:mvf Action or item managed via the MVF production line dedicated to prototypes delivery priority:high High priority for treatment status:confirmed The will to process the item/request of work is confirmed and accepted type:feature Required behavior/compliance waited from a system or technology (performance, architecture, privacy)

Comments

@olivierlemee
Copy link
Collaborator

olivierlemee commented Nov 25, 2022

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:

  • domain event
    • concept
    • unit test
  • process manager
    • concept
    • unit test
  • command
    • concept
    • unit test
  • domain model
    • concept
  • persist
    • concept
    • unit test
  • publisher
    • concept
    • unit test
  • subscriber
    • concept
    • unit test
  • event forwarding through messaging middleware
    • concept
    • unit test
  • notification log and non complex event message-based notification
    • concept
  • event supporting tools and patterns (576) about serializers, immutability, value objects
    • concept
  • cqrs
    • (223)
    • events sourcing (235) + event stores (561)
    • read and write models, querying read model
    • commands and command handlers
    • event and event handlers
    • cqrs command validation
    • event versioning
    • messaging considerations (268)
  • components documentation
@olivierlemee olivierlemee added type:feature Required behavior/compliance waited from a system or technology (performance, architecture, privacy) priority:high High priority for treatment line:mvf Action or item managed via the MVF production line dedicated to prototypes delivery labels Nov 25, 2022
@olivierlemee olivierlemee added this to the OS MVF V0 - Framework milestone Nov 25, 2022
@olivierlemee olivierlemee moved this from Backlog to Planning in Open Source Foundation Pipeline Jan 4, 2023
@olivierlemee olivierlemee self-assigned this Jan 4, 2023
@olivierlemee olivierlemee added the status:confirmed The will to process the item/request of work is confirmed and accepted label Jan 4, 2023
@olivierlemee olivierlemee moved this from Planning to Waiting for design in Open Source Foundation Pipeline Feb 22, 2023
@olivierlemee
Copy link
Collaborator Author

olivierlemee commented Feb 23, 2023

immutable domain event and identification

@olivierlemee
Copy link
Collaborator Author

olivierlemee commented Feb 24, 2023

event store and event sourcing elements coded.

@olivierlemee
Copy link
Collaborator Author

olivierlemee commented Feb 28, 2023

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

  • unit test regarding store (EventStoreUseCaseTest) need to be finalized to validate the mechanism of subscription/auto-notification
  • 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)
  • creation of unit test scenarios using the AccountsManagementServicesImpl model sample with test of command sends with:
    • 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)
    • 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)

@olivierlemee olivierlemee moved this from Waiting for design to Ready for UAT stage in Open Source Foundation Pipeline Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
line:mvf Action or item managed via the MVF production line dedicated to prototypes delivery priority:high High priority for treatment status:confirmed The will to process the item/request of work is confirmed and accepted type:feature Required behavior/compliance waited from a system or technology (performance, architecture, privacy)
Projects
Status: Ready for UAT stage
Development

No branches or pull requests

1 participant