Having gone through a port – to NodeJs – the Ritc rule engine is emerging with some powerful new features and options that make it stand out in the crowd.
In addition to its flexible architecture and its ability to connect via rest to any accessible api, Ritc rules can themselves be treated as microservices through the Ritc api. As a result, Ritc fits naturally into current thinking – and practice – about microservice architectures and deployment.
Secondly, the ability to add new channels by importing Swagger files accelerates your agility in creating new rules – and therefore new microservices. It takes only seconds to import a Swagger file, and minutes – using the Visual Rule Editor – to construct a rule based on the newly-defined channel, whether you are a programmer or not.
Thirdly, the grouping of rules into ‘apps’ and the ability to compose apps – and sub-apps – provides much-needed flexibility as you design your microservices-based architectures. Functional composability is the key to good organization, and a major factor in the scalability of your application.
And finally, the benefits of rules vs hard-coded logic cannot be under-estimated. Rules have a flexibilty that hard-coded logic doesn’t – a factor becoming more significant as the pace of change increases. Hard-coding business logic doesn’t work any more!
Why not consider Ritc for your next project?