Open Source Process engine Snaker

The Snaker workflow engine is designed with a lightweight, simple and smart concept.
First, light weight:
1, can use Jdbc+dbutils independent operation, can also rely on the mainstream IOC, ORM framework to run
2, the entire jar occupies 170K

Second, simple:
1, process components simple.

This has been tangled for a long time, like jbpm including (State/hql/sql/jms/custom/java/script, etc.) really used to have a few. Many components are just accessories, but they increase the cost of learning.
2, table design Simple (currently only 7 tables)
Http://git.oschina.net/yuqs/snaker/wikis/DataBase
In fact, if the various databases support table partitioning better, you can remove 3 tables from the history record.
3. Easy to get started
Just configure snaker.properties/snaker.xml two files according to the actual project environment

Third, Dexterity:
1, extensibility: Exposed more extensible interface, even the core process components (simply add the bean configuration in the Snaker.xml).
2, data persistence level support Jdbc+dbutils, MyBatis, Hibernate, Springjdbc. Currently supported databases are Oracle, MySQL, SQL Server.

Of course, based on the above three point design will certainly lose some of the characteristics of the process engine. So Snaker is currently focused on small and medium-sized projects that require increased workflow characteristics.

Consider Snaker if you have some business in your project that needs to use workflows and feel jbpm, activiti development costs are too high.


The project consists of three parts:
Snaker: Process engine, responsible for scheduling and execution of processes
Snaker-designer: Process designer (plugin based on Eclipse RCP design)
Snaker-web: A suite of case platforms integrated with SPRINGMVC, Shiro, Spring, hibernate
database table Design:
Http://git.oschina.net/yuqs/snaker/wikis/DataBase
Starter Manual:
Http://git.oschina.net/yuqs/snaker/wikis/QuickStart

The following process models are supported:<br>
1, Simple DC:


2. Select Branch:


3. Parallel:


4, sub-process serial:


5, sub-process parallelism:


6, the case of leave process:


The graphical elements of the process designer currently use JBPM-JPDL elements (individuals feel that the icons are more beautiful), as shown below:


Snaker's positioning is simple integration, multi-environment support (advantageous for Project integration workflow in the operations phase). Unlike JBPM, Activiti is not a level (I think these two frameworks are chatty), Snaker is a lite version (because some features are discarded, especially for BPMN support).
In terms of speed, it depends on what ORM is used (mainly on the speed of the place or on the persistence layer). Snaker provides several implementations of Jdbc+dbutils, MyBatis, Springjdbc, and Hibernate.
For details, please refer to:
Wiki:http://git.oschina.net/yuqs/snaker/wikis/home
Source:http://git.oschina.net/yuqs/snaker