rule-engine

I'm supposed to create a simple rule engine in C#. Any leads on how I can proceed?. It's a minimalistic rule engine, and would use SQL server as the back end. Do we have any general blueprint or design patterns that generally apply to rule engines? What kind of .Net technologies can I use to design one? Any directions would be helpful. Thanks. If you're using .NET 3.0 or later, you can use the Rules Engine of Windows Workflow Foundation without having to acutally use Workflow. I've done this on a project, and you can use SQL or XML as the backend, and it works great. You can use the IDE that

I am am working on a project that would benefit from a rules engine. I have consided just using the windows workflow engine, but I would like to know what else is out there. My project has spent most of it's budget. So I would need suggestions to be modestly priced (in the < $1,000 range). I saw InRule , but they don't post prices (that I could see). So I am guessing it is one of those "if you have to ask you can't afford it" kind of products. I saw this post: Looking for simple rules-engine library in .NET But it is old and is focused on Open Source. So, are there any modestly priced .Net

I am looking for suggestions for a lightweight rules engine implemented in Javascript. The reason for such an implementation is to build a very lightweight but fast browser-based simulation using a small set of rules (less than 20). The simulation would take half a dozen parameters and run the rules and display results in the browser without any need to go back to the server. Think of a UI with a couple radio buttons, checkboxes, text boxes and sliders to control the parameters. The simulation would quickly re-run based on any parameter change. I've implemented a (more complicated) version of

I have a pretty decent list of the advantages of using a Rules Engine, as well as some reasons to use them, what I need is a list of the reasons why you should NOT use a Rules Engine The best I have so far is this: Rules engines are not really intended to handle workflow or process executions nor are workflow engines or process management tools designed to do rules. Any other big reasons why you should not use them? duffymo I get very nervous when I see people using very large rule sets (e.g., on the order of thousands of rules in a single rule set). This often happens when the rules engine is

I have an old and deprectaed code of drools, this code can read a rule file (drl) outside of the container and can use any Value Object and any class. CommandExecutor ksession; KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder(); String file = System.getenv("DOMAIN_HOME")+"/mydrls/business.drl"; kbuilder.add(ResourceFactory.newFileResource(file), ResourceType.DRL); KnowledgeBase kbase = kbuilder.newKnowledgeBase(); ksession = kbase.newStatelessKnowledgeSession(); DataTest data = new DataTest(); data.setAge(25); List cmds = new ArrayList(); cmds.add( CommandFactory

I have an application that receives a number of datums that characterize 3 dimensional spatial and temporal processes. It then filters these datums and creates actions which are then sent to processes that perform the actions. Rinse and repeat. At present, I have a collection of custom filters that perform a lot of complicated spatial/temporal calculations. Many times as I discuss my system to individuals in my company, they ask if I'm using a rules engine. I have yet to find a rules engine that is able to reason well temporally and spatially. (Things like: When are two 3D entities ever close?

I'm looking for a simple way to let users define a set of rules to filter objects. Eg. let them define something like "notify me about a booking if booking date < 2009/04/30 AND value > 100.00" More or less: I'd like to have a Ruby rules engine with custom DSL. Is there a library offering that? Came across Ruleby, but it doesn't support custom DSL, yet. What's the best apporach to do that? Ian Terrell Take a look at Treetop . You can define your DSL as a Parsing Expression Grammar and then parse it to create your rules in whatever format you like. Have a look at the wongi-engine gem it is a