Data-driven state machine application
问题 We are currently working on a "data-driven" state machine application. Right now, the state flows are all configured in the database, but none of the decision/business logic is configurable in the DB with our current design. Because of this, the code has to basically "know" the state flow as well, so there's really no point in configuring the flow in the database. I have a design in mind that would allow us to wire together a state pattern using dependency-injection (Spring.NET), but I'm not