I like it so much when a project tells you its limitations in the front page, and compares itself with (and points to) possible alternatives in a useful fashion; it should be standard! But is always awesome! THANK YOU!!
Thanks for sharing, I’m ashamed to admit that I never really “got” these rule engines, but seeing this example finally made things click for me.
Am I correct that there’s a very large overlap between rule engines and workflow engines, and one could use a rule engine like this to implement workflows?
Have you looked into something like BPMN + DMN? BPMN provides workflow modeling and basic decisions, and DMN provides decision tables which can implement more complex rules. There are a couple frameworks which can work on top of that to provide a system implementation.
Exactly this is what I was thinking. We currently have a workflow engine that is event driven + a projection (think: CQRS), and it’s fairly unwieldy. Most specifically, the business logic is defined all over the place, and I was wondering whether a rule engine would make it easier to define the constraints and business logic to act upon these events.
It's from the movie Billy Madison. There was a family of bullies with the last name of O'Doyle, and everytime they picked on someone afterwards they would say "O'Doyle Rules". They eventually had an incident with a banana peel, but you'll have to watch the movie for that one ;)
prob the biggest reason i don't like these type of comments is that the replies will really never be interesting. there is no way for them to be, by nature of the parent not being interesting
and i'm not even shaming you, but finally creating words for my thought when i'm irritated heh
edit: by nature of the parent comment, you are able to unfold the origin of the name (and there was no reference elsewhere). ok, fine then :P
This author is really talented and creates a lot of interesting projects. I spent some time reviewing nightcoders.net and the code quality is really impressive.