Analysis and Market Prediction of three major workflow engines

Technology Analysis and Market Prediction of three major workflow engines 1. starting from Kung Fu, new and new humans will surely think of me as an old man. No, I will not watch movies like kung fu until the end of February this year. But after reading Kung Fu, I think there must be more people: Zhou Xingxing

Why did he have two axes on his chest when he went out to shoot a pole with his fat brother? Find a fake Mountain! The talents installed with axes will not be bullied.

 

 

This reminds me of the previous news: jbpm joins JBoss and becomes JBoss-jbpm. That is to say, jbpm finds a back-to-back JBoss and does not need to wander around in the future.

 

 

Well, let's go to the subject and talk about the three major open-source workflow engines: Shark, osworkflow, and jbpm.

 

 

The back of shark is enhydra. What has enhydra done? More! SlaveJ2EEApplication Server, to o/r mAPPing tool, to this workflow engine, and so on. Why does the persistent layer of shark adopt dods? Because they are family members.

 

 

Jbpm depends on JBoss. The persistence layer of jbpm3 is implemented using hibernate3. This is also the reason. The Graphic Process Definition of jbpm3 has been decided to be embedded into JBoss Eclipse IDE. Let's take a look at JBoss Eclipse IDE Prev.IEVersion 1.5, We can edit a jbpm3 process definition file using a plug-in.

 

 

Osworkflow depends on opensymphony. I like this Organization very much and it has made many good things. When developing the workflow management system, I recommend webwork2. The open-source workflow engine agileflow hosted by the author is implemented based on the WW2 + spring + hibernate architecture.

 

 

Now, basically all J2EE application servers have their own workflow engines, such as enhydra, JBoss, and WebSphere and WebLogic mentioned above, it can be seen that learning workflow engine technology is indeed very important.

 

 

2.

It is impossible to rely on the mountains alone. Isn't Zhou Xing's head flattened by the evil gods after joining the Axe Gang? To save yourself, you still need to be in the palm of your hand.

 

 

The shark Process Definition Language isXPDL, we know that the two most important concepts of xpdl are:ProCess and activity. The activity in xpdl is based on the activity diagram concept in uml1.x. The activity diagram is naturally suitable for workflow modeling. Its biggest advantage over the state chart is that it is easy to implement the Branch Control of concurrent threads. These concurrent threads can be executed simultaneously or sequentially; it also has the advantage of having the concept of swimming channels to control the generation of tasks in the workflow engine. Shark is an activity chart.

 

 

What is osworkflow like? We know that it has an important concept: State ...... Well, we know that it is like FSM. What is FSM ?? Then you are definitely not a good student when you are in college. Of course, if you don't know how to keep it up, you can simply think of it as a state chart. The State in osworkflow is jointly expressed by step and status, and a State is a status in a step. The state conversion is driven by action, similar to the event in the state chart, because an event corresponds to an action.

 

 

Jbpm is no longer as simple as above. It combines the state chart + activity chart + petrinet knowledge, and the activity chart here is also of uml2.0. In the uml2.0 activity diagram, a node is not called an activity but an action. An activity is a high-level concept that contains an action sequence. An activity chart shows a series of actions that constitute an activity. Jbpm also renamed action, called state. The concepts of the status chart used by jbpm include transition/event. Let's take a look. The petrinet concept is also used in the internal implementation of jbpm, such as token and signal. What? What is petrinet? So do you study computer science in college? No? If you have never studied petrinet, take a look at jbpm, we don't have any theory at all. We just need to know the general concept.

 

 

3. It is thankless to make predictions in market forecasts. Many foreign masters are also scolded for making predictions ...... Fortunately, the predictions I made in "Big situation in workflow" last year are still basically correct. At that time, my prediction was: shark ...... Will be on the top of the throne. It should be said that before that article was published, osworkflow was the most popular workflow engine in China. By the end of last year, shark had a significant advantage. I analyzed the following reasons:

 

 

1) Chinese enterprises are interested in xpdl, because it means that they can boast that "we follow WfMC..." in the product manual ......"

 

 

2) Because I boast the "Shark workflow engine's main promoter in China", most of my friends who gave me feedback on the development and selection technologies of the workflow management system use shark.

 

 

3) shark is indeed a good workflow engine. Even if you just want to learn xpdl, you can start from learning shark.

 

 

Now we have reached the era of transition from a feudal society to capitalism in the "Big situation of Workflow". What drives this transformation is not others, but jbpm as mentioned above. Jbpm3 will be released in December March. The final version of jbpm3 will support the core part of BPEL4WS. Therefore, I estimate that shark will be ranked first by jbpm3 after several hundred days of leading the show. The author's open-source agile workflow development framework agileflow will integrate jbpm3 and provide support for the agile engine and jbpm3 engine.

 

 

But is BPEL4WS really close to us? No. I guess it will not really enter our lives this year. When will that happen? This will be the content I want to predict in my next article. I am not sure to mention it now. What I want to consider now is whether I want to boast that "jbpm3 workflow engine is a major promoter in China. (Sysvs)