#Best way to architect ENUM statuses that change in a workflow?

4 messages · Page 1 of 1 (latest)

clear tendon
#

I'm taking a second look at an app that registers a user. As they proceed through the registration process, they get assigned the next appropriate status ENUM (registered, pending, waitlist, entered_event) etc. What's the best way to set up a workflow like this? The ultimate goal is to make a configurable workflow so the app can be customized across several events, so it won't necessarily be the same progress of ENUM every time, ie if one of the events doesn't use a waitlist.

lilac thicket
#

Are you familiar with event sourcing, or seen the commanded lib?

#

If you want to have events be used to derive current state it is one approach to know about

clear tendon