-
Notifications
You must be signed in to change notification settings - Fork 125
Home
The README is having a hard time containing all the great new stuff coming to RuleBook. So, a Wiki was needed to keep it from bursting at the seams.
RuleBook is a great tool for developers looking to get a handle on business logic and abstract it away from application logic. The driving force behind RuleBook is that it should be intuitive; it should work how you work. And in many ways, that's what it does. It provides a simple and intuitive DSL that is incredibly flexible. If you have a larger collection of Rules, they can be built as annotated POJOs and RuleBook can transform the whole package into a RuleBook instantly.
Currently, RuleBook implements a single pattern for chaining Rules: Chain of Responsibility. The benefit of using this pattern, of course, is that it is useful in applications more commonplace than amassing a rules library consisting of millions and millions of rules (yes, that actually does happen). Abstracting a command chain or a workflow is a perfect reason to use RuleBook. Processing dozens or even hundreds of Rules is also a great use for RuleBook. Basically, if you want a solution to the common problems often associated with layered business logic that you can implement in minutes instead of days, or even weeks, then RuleBook is a great solution. And it's getting even better!
Check out the contents of this Wiki to get detailed information on how RuleBook works and how you can start using RuleBook today!