Lightweight State Machine Framework for Order Fulfillment in Xianyu Industry Transactions

Background: Xianyu’s industry products (recycling, consignment, inspection) extend the basic transaction model with additional state‑machine rules, making the order lifecycle far more complex than the simple create → pay → ship → confirm flow.

Problems: The current implementation uses large IF‑ELSE blocks for each fulfillment action, leading to (1) massive, hard‑to‑read methods (hundreds to thousands of lines), (2) duplicated validation and post‑message code, (3) no holistic view of the state topology, and (4) poor extensibility – adding or removing a state requires invasive code changes.

Common needs across industry products include topology queries, execution of state actions with environment‑specific constraints, reproducible execution logs, and unified monitoring.

Solution: Evaluate existing open‑source state‑machine frameworks (spring‑statemachine, squirrel, smart‑engine) and note they assume long‑lived, in‑memory state objects, which does not fit the stateless order‑fulfillment scenario. A lightweight, API‑driven engine is proposed that can define topologies and execute a few core interfaces without heavyweight instance management.

Problem Abstraction: The invariant steps for any state transition are identified as validation, parameter checking, execution, and post‑logic. These steps become a template, while the business‑specific details are injected via interfaces.

State‑Flow Processing: An Executor runs each step (validate → action → postAction) by delegating to a PerformProcessor implementation supplied by the business layer.

Topology Definition: A concise API allows developers to declare the state graph and bind each edge to a PerformProcessor , as illustrated in the diagram.

Framework Structure: Three layers – Core (state topology, query, execution), Glue (adapts core to order services, adds logging/monitoring), and Business (exposes fulfillment APIs per domain such as recycling or inspection).

Benefits: The design isolates complex logic into reusable processors, reduces code size and duplication, provides an automatically generated topology view, and enables simple extensions by modifying the topology definition only.

Conclusion and Outlook: The Xianyu industry transaction team has fully adopted this engine for recycling, consignment, and inspection, achieving unified state control, audit logs, and monitoring. Future work includes automated regression of fulfillment logic and visualized exception tracing.