Case Studies

CronJ has worked with some reputed companies over these years and involved in a number of very challenging tasks. Case studies are available here, just to give you an idea about our expertise on each domain and how we can be part of your next move.

Rule Engine Tool

case study
case study
Problem Statement: An editor to execute custom rules and actions on the database. The system should accept custom rules from the user, within the given limit, and actions should get executed once the given rule gets satisfied.


The implementation of rule-engine now is to check and execute some actions on database. The system takes rules and actions as input and parses the JSON rule to SQL query. The query will be executed and actions will be executed, only if the query returns some result. The actions can be queries as well as something like sending mail, print, etc.

What should the software/system do?
- The Rule component should be very flexible and should accept all kind of metadata to have limit access to the users.
- The query should be very much optimized to process thousands/millions of records.
What should not the software/system do?
- It should not take too much time to process a single rule.
Technologies Used:
  • Node.js
  • React.js
  • PostgreSQL
Why Node.js?
Node.js is highly IO intensive, here we are using file IO and database IO, there is no doubt Node is a perfect choice for IO bound operations.
Why React.js?
React.js is a component based library, so we can resuse the same component over the project, not only over project but also among different projects.
Why PostgreSQL?
Relational database is a better choice for Enterprise application, we thought of that and PostgreSQL supports JSON, ARRAY.

Impact on business:

Rule-engine is used to add some custom business logics to the system. E.g. in e-commerce it helps in offering discounts to some products or some brands.