// the find
aizuda/flowlong
飞龙工作流 FlowLong workflow🐉 真正的国产工作流引擎、json 格式实例模型、仿飞书钉钉审批流程设计器、🚩为中国特色审批匠心打造❗
FlowLong is a Java workflow engine targeting Chinese enterprise approval processes — think DingTalk/Feishu-style multi-person sign-offs, delegation chains, and OA systems. It ships a visual designer, Spring Boot and Solon starters, and MybatisPlus persistence. The feature table is genuinely long: sequential/parallel countersign, vote-weight approvals, proxy, takeback, time-travel backdating — these are real patterns that Activiti/Flowable handle poorly out of the box for Chinese OA contexts.
1. The approval-operation coverage is the best argument for this over Flowable — countersign modes (sequential, parallel, vote-weight), add/remove signers mid-flight, and 'time-travel' backdated approval are baked in rather than bolted on. 2. JSON process model instead of BPMN XML is a pragmatic call for a designer-driven workflow tool; the format is readable, diffable, and doesn't drag in the full BPMN 2.0 surface area. 3. Dual framework support (Spring Boot + Solon) with clean autoconfigure modules means it can drop into the non-Spring Java projects increasingly common in domestic toolchains. 4. PostgreSQL, MySQL, and Oracle DDL scripts are all included, which is more than most workflow libraries bother with.
1. The licensing is a landmine: the 'Apache-2.0 with additional terms' construct is not actually Apache-2.0. The add-on prohibits SaaS redistribution and competing products, threatens ¥1M damages, and auto-escalates to AGPL-3.0 on violation — a lawyer needs to sign off before any commercial use, and most OSS-friendly corporate policies will reject it outright. 2. 776 stars with a commercial 'enterprise edition' dangling over the docs is a warning sign: the open version may be intentionally feature-limited and the roadmap driven by upsell rather than community. 3. No evidence of a distributed-safe scheduler — `LocalLock` is fine for a single JVM, but the absence of a production-grade `RemoteLock` implementation means running multiple instances requires you to bring your own distributed lock or accept duplicate task execution. 4. Documentation is entirely in Chinese with no English equivalent, which is an adoption barrier outside mainland China and makes it harder to evaluate for anyone who can't read it fluently.