Rules Engine
A Novel Process Flow Framework
For most of the customers, it often becomes imperative to execute a set of rules to decide on an outcome. In many cases, customers will need the rules to be executed based on their own data and in a non-sequential manner. This basically means that whether a rule should be executed or not depends on the outcome of one of the predecessor rules. This gets even more complicated when the data set has dependent rules that need to be executed only when certain conditions are met.
All these will require a novel approach that can cater to the disparate needs of customers, while providing an easy way to configure rules, even by citizen developers.
Conclusion
A completely serverless approach was used in designing the rules engine. While AWS was chosen to host this, a cautious approach was adopted to easily migrate to other CSP’s, such as Microsoft Azure.