Spring Statemachine is a framework for application developers to use state machine concepts with Spring applications.
Spring Statemachine aims to provide following features:
Easy to use flat one level state machine for simple use cases.
Hierarchical state machine structure to ease complex state configuration.
State machine regions to provide even more complex state configurations.
Usage of triggers, transitions, guards and actions.
Type safe configuration adapter.
Builder pattern for easy instantiation for use outside of Spring Application context
Recipes for usual use cases
Distributed state machine based on a Zookeeper
State machine event listeners.
UML Eclipse Papyrus modeling.
Store machine config in a persistent storage.
Spring IOC integration to associate beans with a state machine.
State machines are powerful because behaviour is always guaranteed to be consistent, making it relatively easy to debug. This is because operational rules are written in stone when the machine is started. The idea is that your application may exist in a finite number of states and certain predefined triggers can take your application from one state to the next. Such triggers can be based on either events or timers.
It is much easier to define high level logic outside of your application and then rely on the state machine to manage state. You can interact with the state machine by sending an event, listening for changes or simply request a current state.
Quickstart Your Project
|3.0.0 CURRENT GA||Reference Doc.||API Doc.|
|3.1.0-M2 PRE||Reference Doc.||API Doc.|
|3.0.1-SNAPSHOT SNAPSHOT||Reference Doc.||API Doc.|
|2.4.0 GA||Reference Doc.||API Doc.|
|2.3.0 GA||Reference Doc.||API Doc.|
|2.2.2.RELEASE GA||Reference Doc.||API Doc.|