You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UniCore currently implements CQRS (Command Query Responsibility Segregation), DDD (Domain-Driven Design), and Event Sourcing, with working components for event listeners and command dispatchers. However, we lack a unified mechanism that can both listen to emitted domain events and trigger new commands based on specific business logic.
To make better use of what Event Sourcing can offer, we need an internal mechanism (Process Manager?) that can listen to the systems events and fire Commands back in (based on certain business logic).
Motivation
This will allow for a better and cleaner abstraction of the codebase by making better use of Event Sourcing principles.
This abstraction will also remove Application Layer logic away from agent_api_rest
Description
UniCore currently implements CQRS (Command Query Responsibility Segregation), DDD (Domain-Driven Design), and Event Sourcing, with working components for event listeners and command dispatchers. However, we lack a unified mechanism that can both listen to emitted domain events and trigger new commands based on specific business logic.
To make better use of what Event Sourcing can offer, we need an internal mechanism (Process Manager?) that can listen to the systems events and fire Commands back in (based on certain business logic).
Motivation
This will allow for a better and cleaner abstraction of the codebase by making better use of Event Sourcing principles.
This abstraction will also remove Application Layer logic away from
agent_api_rest
Resources
https://martinfowler.com/eaaDev/EventSourcing.html
https://event-driven.io/en/saga_process_manager_distributed_transactions/
To-do List
agent_api_rest
The text was updated successfully, but these errors were encountered: