Dmitry, The short answer is because JBPM is integrated well with Infinispan,the longest and technically correct answer is as follows.
JBPM is now used in many productions of the clients they serve a high number of users.The main problem with the engine of business processes resides in the non- synchronicity of the workflow, ie the workflow goes forward based on the working times of the employees, so it is possible that a workflow ends within a few days. Maintain an instance of a workflow in the database and retrieve it each time it is expensive in terms of time, we might have many workflow latches.The idea is to allow to save in cache the entire instance of a workflow in order to make the most rapid recovery possible. There are also rapid workflows where the use of a cache is very interesting, for example, a job stream must be recovered and carried forward in a few second (for example,at a bank office). The idea is to create a grid of instances of workflows to allow recovery quickly. The idea has already been implemented for Infinispan, but is not very advanced. https://github.com/droolsjbpm/droolsjbpm-integration/tree/master/kie-infinispan/jbpm-infinispan-persistence/src/main/java/org/jbpm/persistence Regards, Gianfranco. 2015-09-28 18:57 GMT+02:00 Dmitriy Setrakyan <dsetrak...@apache.org>: > Gianfranco, > > I am not too familiar with JBPM. Can you make a case on why we may need > this integration and how it will benefit Ignite users? > > Thanks, > D. > > On Mon, Sep 28, 2015 at 6:56 PM, Gianfranco Murador <mura...@apache.org> > wrote: > > > I would like to propose the integration with JBPM , > > I think I can finish in a couple of weeks since I have a bit of time to > > devote to Ignite. > > Let me know if you agree. > > Regards, Gianfranco > > > > 2015-09-28 18:50 GMT+02:00 Dmitriy Setrakyan <dsetrak...@apache.org>: > > > > > I would like to add one more: > > > 10. OSGI integration - Raul Kripalani > > > > > > Raul, hopefully you will have time to finish it. > > > > > > Also, if anyone in the community wants to propose a feature they are > > > working on which can be finished within next couple of weeks, it should > > get > > > into 1.5 as well. > > > > > > D. > > > > > > On Mon, Sep 28, 2015 at 6:43 PM, Yakov Zhdanov <yzhda...@apache.org> > > > wrote: > > > > > > > Guys! > > > > > > > > We have finalized 1.4 release! > > > > > > > > Thanks to everyone involved! That was very important release for our > > > > project. > > > > > > > > Let's discuss scope for 1.5. > > > > > > > > I think the main focus areas should be: > > > > 1. Optimized marshaller rework - Alex Goncharuk works on this. > > > > 2. .Net and Cpp API release (depends on 3) - Vladimir Ozerov > > > > 3. Portable API release - Denis Magda and Vladimir > > > > 4. Failover for continuous query notifications - Nick Tikhonov > > > > 5. Cache Rebalancing optimizations - Anton Vinogradov > > > > 6. Fix compatibility with IBM JDK > > > > 7. Cache stability and performance fixes (as many as possible) > > > > > > > > Nice to have: > > > > 8. Finish vert.x integration - Andrey Gura works on this. > > > > 9. Finish node.js integration - I think Semyon should pass it over to > > > > someone else, given he is busy with cache. Anyone? Andrey Gura? > > > > > > > > Comments are welcome! > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-950 > > > > [2] https://issues.apache.org/jira/browse/IGNITE-1282 > > > > [3] https://issues.apache.org/jira/browse/IGNITE-1258 > > > > [4] https://issues.apache.org/jira/browse/IGNITE-426 > > > > [5] https://issues.apache.org/jira/browse/IGNITE-1093 > > > > [5] https://issues.apache.org/jira/browse/IGNITE-324 > > > > [6] https://issues.apache.org/jira/browse/IGNITE-1526 > > > > [7] https://issues.apache.org/jira/browse/IGNITE-1345 > > > > [8] https://issues.apache.org/jira/browse/IGNITE-1079 > > > > [9] https://issues.apache.org/jira/browse/IGNITE-961 > > > > > > > > --Yakov > > > > > > > > > > > > > > > -- > > Gianfranco Murador > > Igniter and Software Engineer. > > > -- Gianfranco Murador Igniter and Software Engineer.
