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

Demystify combine function - Decider #25

Open
idugalic opened this issue Aug 12, 2021 · 0 comments
Open

Demystify combine function - Decider #25

idugalic opened this issue Aug 12, 2021 · 0 comments

Comments

@idugalic
Copy link
Member

idugalic commented Aug 12, 2021

Explain how to model Commands, Events, and State data types.

  • how inheritance/polymorphism (Sealed and Open) can be used to model OR/SUM relationship and why is this important for modeling Commands and Events
  • what options do we have to model general AND/PRODUCT relationship, and what kotlin idiomatic options do we have (Pairs)
  • explain how combine() function is combining two or more Deciders into one big decider that can just run as a whole. Or you can distribute these deciders via Actors for example and run them in parallel. The decider is a Monoid in respect to the combine() function/operator.
  • Mention the principle of duality (boolean algebra) that is present here.
  • Why do Command and Event have to be nullable (?) in order to be able to use the combine function in the first place.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant