CacheControl / CacheControl/json-rules-engine

version 7 - Design

未关闭
#372 9 条评论 3 个 reaction 已指派 0 人 在 GitHub 查看
next-major
主要语言
JavaScript
星标
3.1k
派生
507
PR 合并指标
30 天内没有已合并 PR

描述

Starting a thread here to put notes on a version 7 design.
Version 7 is an opportunity to make a number of changes that have been suggested in issues filed here that would make the JSON rules engine more extensible at the cost of breaking backwards compatibility with the current 6.x versions.

### Extensibility vs. Structure
With version 7 we want to consider the tradeoff between extensibility and having a known structure. For instance introducing the ability to add custom `Condition` classes or custom `Rule` subclasses allows for the system to be highly extensible but makes it much harder to reason about the input and output of the rules engine without knowing about all these extensions.

Ultimately we need to draw this line somewhere and my initial inclination is to draw it in favor of more extensibility in order to allow the broadest possible use of the rules engine.

### Concepts
Starting from a clean stale the following basic concepts will be part of the rules engine

**Facts**
Facts are things that are known by the rules engine during execution.

**Almanac**
The Almanac is the system for storing and looking up `Facts`.

**Conditions**
Conditions are executable, contain a priority, and return a result containing a boolean value. Generally there are 2 types of conditions, comparison conditions which check the value of a fact against another value, and composite conditions like `all`, `any`, and `not` which use 1 or more nested conditions to produce a result. By being fully extensible it's possible to introduce other types of conditions.

**Rules**
Rules are also executable and contain a priority. They generally are comprised of a set of conditions which are executed. Rules produce events as a result of execution.

**Engine**
The engine provides the mechanism to evaluate rules, and conditions. It includes mechanisms to resolve the values of facts or other special objects. Changing the engine can significantly change the behavior of the system.

贡献指南

这个仓库没有索引到贡献指南

调研方向

这是一个版本 7 的设计讨论,而不是实现任务,其中没有指定任何文件、测试或入口点。请先查看当前的 6.x 规则引擎以及讨论中引用的相关 Issue;要完成这项工作,需要就可扩展性、结构、Facts、Almanac、Conditions、Rules 和 Engine 达成一致的设计。

由索引模型根据 Issue 内容生成。

评估

技术栈
javascript
领域
backend
Issue 类型
功能
难度
5/5
预计耗时
一周以上
活跃度
停滞
描述清晰度
需要澄清
新手友好度
20/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。