Comparison between the Rules Engine ILog and CKRule, and the engine ilogckrule

Comparison between the Rules Engine ILog and CKRule, and the engine ilogckrule

IBM™WebSphere™ILOG is the most influential business rule commercial software in the industry. It provides the best business rule management system and has a wide range of success stories in the Java field. There are a lot of technical information about ILOG on the Internet. Everyone knows the components and functions of ILOG. The following is a simple comparison between ILOG and CKRule, so that you can better understand the functions and usage of CKRule.

  Positioning  As the most successful business rule Management System (BRMS), ILOG has its mature system structure and standard architecture. However, it is not an object for CKRule learning. CKRule is based on a lightweight rule engine/BRMS. It can be implemented through the simplest interface with minimal deployment and quick settings. ILOG is based on large-scale business rule applications, while CKRule is agile and lightweight.

	WebSphere ILOG	CKRule
Positioning	Large-scale commercial use	Agile and lightweight
Deployment	Requires Web server support	Can be deployed as a service or directly referenced by DLL
Language	Java,. Net, C ++ and other comprehensive support, Java is the most mature.	Only. Net is supported.
Write	Use Eclipse to write basic scripts	Use CKRule's built-in Editor
Price	Like an IBM server	Like PCs in China
Learning	High learning cost	For those who know C #, there is basically no cost.

Reference  It is the main part of the ILOG business Rule management system, including Rule Studio, Rule Tean Server, Rule Scenario Manager, and Rule Execution Server.
And CKRule functions.

ILOG part	Function Description	CKRule reference
Rule Studio	An Eclipse-based rule design and development environment. For developers.	Ckruleregular Editor, which uses the program interface started by ckboot.exe. For developers, implementers, and system administrators.
Rule Team Server	Business Rule maintenance interface. Used by business experts.	The customer rule pool interface needs to be developed by the Business System as needed. Used by business experts.
Rule Scenario Manager	Test and simulate functions.	CKRule test function.
Rule Execution Server	Business Rule execution server. Allows you to modify rules during running.	CKRule RuleFacade interface. Allows you to modify rules during running.

ILOG is a heavyweight system-wide product, while CKRule is only a lightweight middleware. The two have similar core functions, but their positioning varies widely. CKRule not only solves the problem of business rules, but also has a hard time working on dynamic code. It is a combination of multiple functions and allows you to use simple and effective scripts to dynamically modify the interface or data, is a typical multi-function economic product.
What is the real rule engine?

Many people may not know what the rule engine is, or what it actually uses. We all know the workflow engine, and we have heard of Drools under JBoss, or we know that weblogic or Oracle also has their own Business Rule. We may have heard that ILOG was acquired by IBM, if we study Microsoft's WWF, we may also know RuleSet and so on. Some domestic web quick development platforms also mention the rule engine.
In our impression, we feel that the rule engine solves the implementation problem of the business logic layer. Therefore, we naturally think that the logic processing of a node in a workflow should be implemented by the rule engine, so the logic of the workflow itself should also be solved by the rule engine. In addition, we also feel that the business logic of projects should be solved by the rule engine.
However, when we use these rules engines, we find it difficult to correspond to the business logic implementation at the business logic layer we actually apply.
Taking Drools of JBoss as an example, because its rule engine uses the matching rule method, when these rule engines are applied. First, we need to abstract the business logic in our specific application into a rule, and then package it into a rule package. A rule package is equivalent to a smart block. After the data is transmitted to the smart block, the system will apply the logical processing that meets the conditions in a matching manner.
When using this method, we should say that the logic is more abstract and abstract at a higher level. However, the application of the rule engine has been greatly restricted.
First, this abstraction requires a complex analysis process, which requires strong analysis and design capabilities. In addition, the business logic layer in our specific applications usually processes a large amount of actual data. In most cases, it is a batch data processing, some logic parameters cannot be defined in rules, but are configured in database tables. Therefore, the development of common business logic layers cannot first design a data model and then abstract the logic on this basis.
Therefore, we found that Drools and other rule engines are difficult to use, not what we need.
We have been studying the rule engine for some time. Sometimes we find that our own rule engine is not a rule engine. Because we are very different from rule engines like Drools. However, we did solve the problem of business logic configuration at the business logic layer. It should be said that we are more practical. However, we cannot implement the JSR94 standard. We not only process the business logic, but also all the operations to be processed at the business logic layer are configured in the form of rules, including the database processing logic.

Who can introduce some books on the rule engine?

Rule Engine-Based Enterprise Service Development Model
Tao Xiaojun, Zhu Min
(Computing Center, School of information science and technology, East China Normal University, Shanghai 200062, China)
Abstract: This article explores and proposes a set of development modes followed by effective use of the rule engine technology to develop enterprise service application systems, this includes designing an enterprise service model based on the Rule engine, and proposing the specific steps and methods for implementing enterprise service applications using the rule engine technology, which is closely integrated with the Rule Engine idea in the actual development process.
Keywords: Rule Engine JSR-94 Rete algorithm Drools
Pattern of Building Enterprise Services with Rule Engine
TAO Xiao-jun, ZHU Min
(Computer Center, East China Normal University, Shanghai, 200062, China)
Abstract: This article will study and advance a pattern which is based on the idea of rule engine for practical building enterprise services that using rule engine technology implements tively and handy. the pattern provided des a model of enterprise services based on rule engine, and the step and process of developing enterprise services using rule engine technology.
Key Words: Rule Engine JSR-94 Rete Arithmetic Drools
1. Introduction
The rule engine is a software system used to manage and automatically implement business rules. Its main function is to store, classify, and manage rules, verify rule consistency, and infer other rules through rules, the application of the contact rules and the execution of these rules. The rules mainly refer to the business or business logic, legal terms, and enterprise policies. the concept of rule engine is to separate commercial rules from the application logic of software to realize the flexibility of commercial applications. in the traditional enterprise service application development mode, the business logic is directly fixed in the application code, which makes the application maintenance complex and expensive, changing business rules and business processes always cause frequent changes to applications, especially when facing the challenges of dynamic business models and business processes, applications developed in traditional mode often face comprehensive and costly modifications and even design changes. to solve this problem, we need to adopt a new development mode to strip the business logic from the code layer. the rule engine provides a system development architecture that separates business processing from business rule processing, shares and uniformly manages and maintains business rules. this article describes the Rules Engine-based enterprise service application development model, including the rules engine-based enterprise service model and basic development steps and methods.
2. Rule Engine-Based Enterprise Service Model
Designing a clear and effective system model is a prerequisite for the smooth operation of enterprise service systems. figure 1 a simple architecture of enterprise service applications developed based on the Rules Engine and Its Pattern conforming to JSR-94 standards is designed.
Figure 1
The enterprise service system described in Figure 1 is divided into three parts:
Application/Data Acquisition System: This system captures and stores all data submitted by applications and serves as a user of business services. Its main function is to submit business requests and process business decisions.
Service: Call the selected rule engine to execute the business rule logic or perform operations on the Business Rule logic through the network server or API that can be called to generate feedback information and data. it also provides convenient and effective maintenance of business rule logic.
Support Service: submit the full text of ......>