1

Topic: Advise built in workflow engine

Is Spring-based service. Service has some "long-playing" tasks consisting of set of serial steps. Each step can be fulfilled on some minutes. Here these here sequences of steps need to be fulfilled, despite stops and shut-downs - i.e. after shut-down we are launched and it is extendable therefrom where were interrupted. Sounds as quite typical task for Workflow Engine (do not know how it in Russian to name).  - ready engines the heap is mentioned, but the most part of lists and reviews strongly give naphthalene. Can recommend something, by the experience? Or to prompt, it is not necessary to potter with what engines. From requirements: -  for commercial usage - , not demanding to open the source codes (i.e. not GPL) - . The engine should be in storage, and given to store on a disk, without a database. - Well and ease of use, was easier to use an indirect engine, than  on a knee the bicycle.

2

Re: Advise built in workflow engine

Hello, Artem Korneev, you wrote: AK> Is Spring-based service. Service has some "long-playing" tasks consisting of set of serial steps. Each step can be fulfilled on some minutes. Here these here sequences of steps need to be fulfilled, despite stops and shut-downs - i.e. after shut-down we are launched and it is extendable therefrom where were interrupted. It is not assured that in accuracy it is necessary to you but is BPMN for long-playing tasks and there is  https://github.com/camunda It quite to herself is built in simply, did couple of years back. The state stores in a DB. But it is all a severe enterprise it is not assured that it is necessary to you but formally approaches under conditions.

3

Re: Advise built in workflow engine

Hello, GarryIV, you wrote: GIV> the State stores in a DB. Here behind itself it would not would be desirable to drag a database. I will add to requirements.

4

Re: Advise built in workflow engine

Hello, Artem Korneev, you wrote: AK> Is Spring-based service. Service has some "long-playing" tasks consisting of set of serial steps. Each step can be fulfilled on some minutes. Here these here sequences of steps need to be fulfilled, despite stops and shut-downs - i.e. after shut-down we are launched and it is extendable therefrom where were interrupted. AK> sounds as quite typical task for Workflow Engine (do not know how it in Russian to name).  - ready engines the heap is mentioned, but the most part of lists and reviews strongly give naphthalene. AK> can recommend something, by the experience? Or to prompt, it is not necessary to potter with what engines. From requirements: AK> -  for commercial usage AK> - , not demanding to open the source codes (i.e. not GPL) AK> - . The engine should be in storage, and given to store on a disk, without a database. AK> - well and ease of use, was easier to use an indirect engine, than  on a knee the bicycle. Spring Batch, but the interrupt logic and other needs to be programmed most.

5

Re: Advise built in workflow engine

JBPM, it truth stored the data in basis, , can is adjusted, under requirements like approaches.

6

Re: Advise built in workflow engine

Hello, Artem Korneev, you wrote: GIV>> the State stores in a DB. AK> here behind itself it would not would be desirable to drag a database. I will add to requirements. It is possible to try to fasten to embeddable basis. On a disk there will be a same one file.

7

Re: Advise built in workflow engine

Hello, Artem Korneev, you wrote: AK> Is Spring-based service. Service has some "long-playing" tasks consisting of set of serial steps. Each step can be fulfilled on some minutes. Here these here sequences of steps need to be fulfilled, despite stops and shut-downs - i.e. after shut-down we are launched and it is extendable therefrom where were interrupted. Here without basis not to manage. As a rule superficial Workflow Engine use  bases, for example h2db AK> Can recommend something, by the experience? Or to prompt, it is not necessary to potter with what engines. From requirements: AK> -  for commercial usage AK> - , not demanding to open the source codes (i.e. not GPL) AK> - . The engine should be in storage, and given to store on a disk, without a database. AK> - well and ease of use, was easier to use an indirect engine, than  on a knee the bicycle. Recently, from superficial, tried Flowable,  Activiti. A low threshold of entrance, the good documentation, a live forum. BPMN the designer. Truth since JDK8 +

8

Re: Advise built in workflow engine

Hello, Artem Korneev, you wrote: AK> Is Spring-based service. Service has some "long-playing" tasks consisting of set of serial steps. Each step can be fulfilled on some minutes. Here these here sequences of steps need to be fulfilled, despite stops and shut-downs - i.e. after shut-down we are launched and it is extendable therefrom where were interrupted. AK> sounds as quite typical task for Workflow Engine (do not know how it in Russian to name). If it is necessary to lose simply set of serial steps any message queue approaches. It is possible with persistance (if it is necessary to be recovered after service falling), all is possible in storage. If already there is a basis and reliability it is possible to look on dbqueue from Yandex is necessary. Money. If the basis is not present, any ActiveMQ or RabbitMQ, but there all the same any basis for persistance is required. AK> - . The engine should be in storage, and given to store on a disk, without a database. And than a database - not the data on a disk? Only with reliable storage. Engines without basis - most likely will be the crude hand-made articles which are not providing any warranties on end of a step, to recovery, etc.

9

Re: Advise built in workflow engine

Hello, Artem Korneev, you wrote: AK> Can recommend something, by the experience? Or to prompt, it is not necessary to potter with what engines. From requirements: Pens, pens. WF Engines do not justify the forces enclosed on their fastening in the project.

10

Re: Advise built in workflow engine

AK>> Can recommend something, by the experience? Or to prompt, it is not necessary to potter with what engines. From requirements: a C> Pens, pens. WF Engines do not justify the forces enclosed on their fastening in the project. Porridge from an axe as a result turns out

11

Re: Advise built in workflow engine

Hello, bzig, you wrote: AK>>> Can recommend something, by the experience? Or to prompt, it is not necessary to potter with what engines. From requirements: a C>> Pens, pens. WF Engines do not justify the forces enclosed on their fastening in the project. B> porridge from an axe as a result turns out And at fastening WF - monster Frankenshtejna.

12

Re: Advise built in workflow engine

B>> Porridge from an axe as a result turns out a C> And at fastening WF - monster Frankenshtejna. Fastening WF Engine == porridge from an axe in which itself WF is an axe.

13

Re: Advise built in workflow engine

Hello, Artem Korneev, you wrote: AK> Is Spring-based service. Service has some "long-playing" tasks consisting of set of serial steps. Each step can be fulfilled on some minutes. Here these here sequences of steps need to be fulfilled, despite stops and shut-downs - i.e. after shut-down we are launched and it is extendable therefrom where were interrupted. AK> sounds as quite typical task for Workflow Engine (do not know how it in Russian to name).  - ready engines the heap is mentioned, but the most part of lists and reviews strongly give naphthalene. From us in office for guiding of projects bought any super-adjusted vork-flou  for the mad grandma. Its two programming teams already adjust half a year

14

Re: Advise built in workflow engine

Hello, vsb, you wrote: GIV>>> the State stores in a DB. AK>> here behind itself it would not would be desirable to drag a database. I will add to requirements. vsb> it is possible to try to fasten to embeddable basis. On a disk there will be a same one file.  from a box is able H2, basically with jdbc it is possible to fasten any DB.