🚩This is 2024, and I cannot believe we have developers with 10+ years of experience who do not know what a rule engine is, let alone a decision engine or decision management suite.
So let me explain it here for my fellow #developers #coders #programmers …
When the system or application you are developing is running in a regulated environment or is based on policies and laws of a region, state etc. then…
1️⃣ you need to abstract the business rules out that allow you to update them independently and individually
2️⃣ you need to make sure all types of business rules (selection, choices, validation, calculation, etc.) based on legislation and laws are to be updated quickly without any application or system coding and redeployment
3️⃣ you need to be able to delegate the creation and updating of the business rules to non-programmers and domain experts with no coding/programming background
That's where the concept of a business rules engine or BRE comes into the picture!
Here is when it gets complicated. You need to be able to meet all three of the above requirements. Otherwise, the BRE becomes just another software component (or architecture layer) inside the whole application and will be treated as another developer's tool in their toolbox.
Why do we do all of these?
🚀The core reason from a software engineering and design viewpoint is the separation of concerns. With this principal in mind, it essentially separate the life cycle of business rules from the actual application code. Allowing them to be created and updated independent of application code and any application deployment.
Learn more about separation of concern and BRE at https://lnkd.in/gPZf-dFk
#csharp #python #rust #java #javascript #golang
Posted here.
Published July 9th, 2024 at 07:30 am
