With the latest version of Imixs-Workflow we support now a consistency Lucene search index coupled with the Java EE container based transaction concept.
Writing a Lucene Index during a Java EE transaction, coupled to JPA database operations, it becomes quickly difficult to keep the Lucene index consistent. The reason is that a lucene index can become inconsistency if you write the lucene index within a long running Java transaction. In case the transaction fails lately, there is no way to roll back the already written lucene index automatically. This is different to the build-in roll-back functionality of a SQL database which is only writing new data in case the transaction succeeds. Also clients reading the index before a running transaction is closed will read uncommitted index data which will lead to wrong search results. Continue reading “Lucene Index Consistency”
The next major release of Imixs-Workflow 4.0.0 is already under development and will be released soon. The new version represents a significant improvement in performance and stability. One of the major improvements is the new database schema as well as the integration of the Lucene Search Technology. At the same time, we will also re-factor the service layer which will simplify the usage of Imixs-Workflow for most projects.
For software companies and larger projects, Imixs-Workflow can be a huge improvement in changeability and cost reduction for the development of enterprise business applications. The BPMN 2.0 standard and the Imixs-BPMN modeler allows to change business logic during runtime and simplifies the way to maintain complex business applications.
The new release which is now in a test stage will be released in September 2016. You can join the project on GitHub.