Skip to content

Event Sourcing semantics with Allium? #85

Description

@tburny

Hi there,there is one thing I am really struggling with the whole time: How do I express event sourcing semantics as in "decider pattern" with commands and events in Allium?

From what I understand Allium is great for state based transitions. But it's weak spot is the conflation of the event and the transition that follows it.

So allium is state -> behaviour -> state. But event sourcing is command + state -> events and then event + state -> state.
Basically these two become one step in allium when it is actually two.

Am I getting something wrong here?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions