低代码平台

everywhere.z 7a7a9ef64d bug #I5C23U 子流程用getChainName取不到当前ChainName的问题 3 年之前
liteflow-core 7a7a9ef64d bug #I5C23U 子流程用getChainName取不到当前ChainName的问题 3 年之前
liteflow-script-common 7a7a9ef64d bug #I5C23U 子流程用getChainName取不到当前ChainName的问题 3 年之前
liteflow-script-groovy 7a7a9ef64d bug #I5C23U 子流程用getChainName取不到当前ChainName的问题 3 年之前
liteflow-script-qlexpress 7a7a9ef64d bug #I5C23U 子流程用getChainName取不到当前ChainName的问题 3 年之前
liteflow-spring 7a7a9ef64d bug #I5C23U 子流程用getChainName取不到当前ChainName的问题 3 年之前
liteflow-spring-boot-starter 7a7a9ef64d bug #I5C23U 子流程用getChainName取不到当前ChainName的问题 3 年之前
liteflow-testcase-declare-component 7a7a9ef64d bug #I5C23U 子流程用getChainName取不到当前ChainName的问题 3 年之前
liteflow-testcase-nospring 7a7a9ef64d bug #I5C23U 子流程用getChainName取不到当前ChainName的问题 3 年之前
liteflow-testcase-script-groovy 7a7a9ef64d bug #I5C23U 子流程用getChainName取不到当前ChainName的问题 3 年之前
liteflow-testcase-script-qlexpress 7a7a9ef64d bug #I5C23U 子流程用getChainName取不到当前ChainName的问题 3 年之前
liteflow-testcase-springboot 7a7a9ef64d bug #I5C23U 子流程用getChainName取不到当前ChainName的问题 3 年之前
liteflow-testcase-springnative 7a7a9ef64d bug #I5C23U 子流程用getChainName取不到当前ChainName的问题 3 年之前
static c7f9062040 更新readme 3 年之前
.gitignore d86369b30c init 7 年之前
LICENSE e23ad13dd0 Initial commit 7 年之前
README.md c7f9062040 更新readme 3 年之前
README.zh-CN.md c7f9062040 更新readme 3 年之前
pom.xml 7a7a9ef64d bug #I5C23U 子流程用getChainName取不到当前ChainName的问题 3 年之前

README.md

logo

Your star is my motivation to keep going. If you like LiteFlow, please help me with a star in the upper right corner.

Overview

liteFlow is a lightweight , fast component-based process engine framework / rules engine , component orchestration , component reuse , to help decouple business code , so that each business fragment is an elegant component , and support hot-loading rule configuration , to achieve on-the-fly modification .

Website url: https://liteflow.yomahub.com

Documents url: https://liteflow.yomahub.com/docs

Example projects: https://gitee.com/bryan31/liteflow-example

Feature

  • Component definition unified: All logic is a component, for all logic to provide a unified component implementation, small size, large energy.
  • Rules lightweight: based on the rules file to arrange the process, learning the rules entry only takes 5 minutes, a read both understand.
  • Rule diversification: rules support XML, JSON, YML three rule file writing methods, which you like to use.
  • Arbitrary arrangement: Synchronous asynchronous mixing, no matter how complex the logic process, using LiteFlow rules, are easy to do, see the rules file to see how the logic works.
  • Rules can be loaded from anywhere: The framework provides implementations of local file configuration sources and ZK configuration sources, as well as an extension interface that allows you to store rules anywhere.
  • Elegant hot refresh mechanism: Rule changes, instant change of application rules without restarting your application. High concurrency does not cause any errors in executing rules due to refreshing rules.
  • Wide support: LiteFlow works regardless of whether your project is built on Springboot, Spring, or any other Java framework.
  • JDK support: From JDK8 to JDK17. Don't worry about JDK versions.
  • Scripting language support: Scripting language nodes can be defined, supporting both QLExpress and Groovy scripting. More scripting languages will be supported in the future.
  • Rule nesting support: You can use simple expressions to create multiple nested complex logic layouts if you want.
  • Component retry support: Components can support retry, and each component can customize the retry configuration and specify exceptions.
  • Context isolation mechanism: Reliable context isolation mechanism, you do not have to worry about high concurrency data flow.
  • Declarative component support: You can make any of your classes become components in seconds.
  • Detailed step information: How your link performs, how much time each component takes, what errors are reported at a glance.
  • Stable and reliable: has been iterating for more than 2 years, running stably on the core systems of major companies.
  • Excellent performance: the framework itself consumes little extra performance, depending on the efficiency of your component execution.
  • Built-in simple monitoring: Built-in a command line monitoring framework, you can know the running time ranking of each component.

WECHAT OFFICIAL ACCOUNT

Since the community group is over 200 people, you need to be invited to join the group. Follow the WECHAT OFFICIAL ACCOUNT and click Personal WeChat to add me, I can invite you into the group

offIical-wx

Open source is not easy, please sponsor LiteFlow if you support it

support