Objective: The primary use case is being able to expose business logic to
non-technical users. This logic is traditionally hidden within code. ODM
exposes the logic out to the business users for them to be able to
manage it over time without IT involvement.
Before ODM, all the rules were configured on legacy
systems we're transforming all this into a new set of technologies such
as REST microservices, cassandra and with IBM ODM so that Business Users will be able to easily change the rules.
Deployment is done on the client-side only. Business User can update rules through UI
I have used it for few projects in which number of business logic rules varied from the 70 to about 1,800 rules.
There is an increase in productivity, agility and responsiveness because after it is configured once in the environment, Business User can deploy the rules and configuring the rules and making the changes by themselves. Deployment failures have happened very few times. (So far, twice only). Only then do we get a call: "We are experiencing issues." So productivity, being on the developer side has improved because once I have configured the rules, I don't have to worry about them. I have time to work on other things. The Business User is able to keep changing the rules and it is very easy for them. The client is very happy.The
result is a step toward creating a more modern infrastructure, to evolving business
needs.
Apart from the cost savings, efficiency has also increased. I never thought we would be able to develop that amount of change, it is now near real-time; being from the It used to be a very time-consuming process.
Now, As soon as Business User deploys a rule, well... it gets deployed.
There's more, they can even use an Excel sheet for input for updating the rules.