What is the difference between drools and jbpm

I see it as a dependency problem. It's a narrow distinction, but a definite one. I see global problems as in global variables which are not enforced, and as such create a soft global dependency. But a hard-coded class creates an enforced dependency, and as such create a hard global dependency.

So both are dependencies. But I consider the global to be far worse since it's not enforced Which is why I don't like to lump class dependencies with global dependencies under the same banner This creates a hard-coupling, which makes your code less flexible, and as such should be avoided. However, interfaces exist to permit exactly this type of coupling. With that said, I wouldn't introduce an interface just to add a constant to it. So if you're using interfaces, and you're very sure that you or anyone else for that matter won't need additional values, then I don't really see a huge issue with the interface constants The best designs wouldn't include any constants or conditionals or magic-numbers or magic-strings or hard-coded anything.

However, that adds additional time to the development, as you must consider the uses. My view is that most times it's absolutely worth taking the additional time to build a great solid design.

But there are times when good enough really is acceptable and it takes an experienced developer to understand the difference , and in those cases it's fine. In some way they serve to the same purpose. We made sure that it covers most of what is needed when you are running business processes. For rules there is a different multi purpose execution server that is being developed and it is targeted to 6. If you are looking for a purely Rules execution server you can take a look at the drools camel server or get in contact and try the latest snapshots of the new work that is being done.

Kris Verlaenen Maciej Swiderski Geoffrey De Smet Edson Tirelli Michael Neale Tihomir Surdilovic Salaboy Eder Ignatowicz Marian Buenosayres Manaswini Das William Siqueira Karina Varela Guilherme Carreiro Luiz Motta Matteo Mortari Paulo Martins Mario Fusco Sotty 9. Cristiano Nicolai 9. Guilherme Caponetto 9. Toni Rikkola 8. Edoardo Vacchi 8. Tiago Bento 6. Francisco Javier Tirado Sarti 6. Gabriele Cardosi 5. Jacopo Rota 5. Tommaso Teofili 5. Sadhana Nandakumar 5.

Michael Anstis 4. Alessandro Costa 3. Luca Molteni 3. Please could you provide me more information and your experience with one or other and what do you think is the best to use to manage business rules. Drools is a rule engine. So Drools is what you're looking for. Drools and jBPM are companion projects: they integrate really nicely if you need workflows with rules.

Drools is a Rete rules engine that does forward and back induction. You can use it in a small setting for local decisions that only require a handful of rules OR something as large as an underwriting decision engine in insurance. Think of the Mediator pattern in GoF.