How To Choose a Rules Engine

Helping IoT solution architects, engineers and product managers to understand how to choose a rules engine that perfectly fits their solution requirements.

Download
<style> #drip-ef-103284675 { font: .875rem/1.5rem sans-serif; width: 100%; } #drip-ef-103284675 h3 { font-size: 1.125rem; margin: 0 0 .375rem; } #drip-ef-103284675 > div { margin-bottom: .75rem; } #drip-ef-103284675 fieldset { border: none; margin: 0; padding: 0; } #drip-ef-103284675 legend { margin: 0; padding: 0; } #drip-ef-103284675 input[type="email"], #drip-ef-103284675 input[type="number"], #drip-ef-103284675 input[type="tel"], #drip-ef-103284675 input[type="text"] { margin: 0; padding: .375rem .5625rem; width: 100%; } #drip-ef-103284675 input[type="checkbox"], #drip-ef-103284675 input[type="radio"] { margin: .1875rem .1875rem 0 0; padding: 0; } #drip-ef-103284675 input[type="submit"] { margin: 0; padding: .375rem .5625rem; } </style> <form action="https://www.getdrip.com/forms/103284675/submissions" method="post" data-drip-embedded-form="103284675" id="drip-ef-103284675"> <h3 data-drip-attribute="headline">How To Choose a Rules Engine</h3> <div data-drip-attribute="description">Fill-in the form to download the white paper!</div> <div> <label for="drip-email">Email Address</label><br> <input type="email" id="drip-email" name="fields[email]" value=""> </div> <div> <label for="drip-first-name">First Name</label><br> <input type="text" id="drip-first-name" name="fields[first_name]" value=""> </div> <div> <label for="drip-last-name">Last Name</label><br> <input type="text" id="drip-last-name" name="fields[last_name]" value=""> </div> <div> <label for="drip-job-title">Job Title</label><br> <input type="text" id="drip-job-title" name="fields[job_title]" value=""> </div> <div> <label for="drip-company">Company</label><br> <input type="text" id="drip-company" name="fields[company]" value=""> </div> <div> <label for="drip-phone">Phone Number</label><br> <input type="text" id="drip-phone" name="fields[phone]" value=""> </div> <div> <label for="drip-iot-project-requirements">Do you have any questions for us?</label><br> <input type="text" id="drip-iot-project-requirements" name="fields[iot_project_requirements]" value=""> </div> <div style="display: none;" aria-hidden="true"> <label for="website">Website</label><br> <input type="text" id="website" name="website" tabindex="-1" autocomplete="false" value=""> </div> <div> <input type="submit" value="Download" data-drip-attribute="sign-up-button"> </div> </form>

When developing IoT apps, building the business logic by configuring rules straight into the code is suboptimal. Using a rules engine is the better way, if the engine is chosen correctly.

When choosing, it’s good practice to look at how powerful the rules engine is (its depth of functionality), how easy it is to use (its level of complexity) and how ready it is to support your future needs (based on your growth trajectory and features you may need).

In this paper, we have defined a testing benchmark composed of seven such capabilities, to help you evaluate rules engines when looking at automating for IoT.

Download our paper to learn more.