Skip to content
This repository has been archived by the owner on Jun 22, 2022. It is now read-only.

Discussion: Sentinel #97

Open
ryan-mars opened this issue Jul 12, 2021 · 0 comments
Open

Discussion: Sentinel #97

ryan-mars opened this issue Jul 12, 2021 · 0 comments
Labels
discussion enhancement New feature or request event-storming Fluent components for translating event storms to code
Milestone

Comments

@ryan-mars
Copy link
Owner

This issue is for discussion of the Sentinel Concept

Policies can maintain their own state? Reminds me of our Sentinel concept.
@sam-goodwin

Early on I wondered if we should have policies that maintain state and I wondered if this could be done using Step Functions. Our discussions are pointing in the direction that there is a special kind of Policy that watches a Read Model for work. This fills an important gap in implementing Event Sourced applications where eventual consistency can lead to "work not done"
or "cleanup" required in some business processes. It seems like this centers around some kinds of race condition (e.g. assigning time-sensitive work to an employee who just went on break).

During Event Storming I propose that this be treated as a simple Policy (lilac sticky note) however during implementation we differentiate between Stateless and Stateful Policies.

@ryan-mars ryan-mars added discussion enhancement New feature or request event-storming Fluent components for translating event storms to code labels Jul 12, 2021
@ryan-mars ryan-mars added this to the 1.0 milestone Jul 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
discussion enhancement New feature or request event-storming Fluent components for translating event storms to code
Projects
None yet
Development

No branches or pull requests

1 participant