Business rules are there to serve the business of the client to whom you are building the application for.As rules evolve, you will find yourself stuck with tens of entries distributed over multiple configuration files. Think about it: you start adding key-value pairs into configuration files and reading them in your code. Now, while this would be a perfectly acceptable technical solution, it is far from being ideal. You might think “configuration files”.And since business rules do change in real life, this would quickly turn into a nightmare. Once you have your business rules “hard-coded” in your application, any future change for a certain rule will result in changing the code, compiling, and deploying.
Modeling these business rules inside the application code directly adds several maintenance and operation challenges: IntroductionĪll applications include business rules (at least they should).
This article is for two sets of readers: those who are new to Microsoft Business Rule Engine and are looking for a direct hands-on approach rather than going though the theory and architecture behind BRE (links for that at the Additional Resources section), and those who are familiar (but not experts) with the topic in general, and are looking to understand, in a practical manner, how to program with BRE and leverage some of its powerful offerings.