GoRules Engine
GoRules' own agent, running the rules you release in the BRMS.
Category: Business Rules
GoRules Engine runs the GoRules agent (version 2.0.1), the service GoRules ships for executing decision models in production. It has no screen of its own. Other apps on your site call it, hand it the facts, and get a decision back.
What it does
- Loads released decision models from its storage and checks for new or changed ones continuously, so a new release takes effect without a restart.
- Evaluates decision tables and graphs deterministically for any app that calls it: Node-RED, n8n, Ignition, or your own code.
- Keeps working offline. With the default storage, the rules live on the node.
When to use it
Use GoRules Engine next to the equipment that needs decisions, with GoRules BRMS as the place those rules are written and released. If you want a smaller engine that evaluates JDM files you supply directly, see GoRules ZEN Engine.
Running on EmberNet
- Headless. The card shows the engine running, with nothing to open. Apps on your site call it directly.
- One instance per node.
- Rules kept on the node. By default the engine reads rules from storage on the node. It can read from S3, Google Cloud Storage, or Azure Storage instead when a fleet should share one source of releases.
- Small footprint.