What are the reasons for porting drools to .Net using IKVM? We are considering using Drools.Net in a project, but the use of IKVM is preventing this. One approach may be for us to port the entire codebase to .Net and submit back to the community. Are there some fundamental issues that force the use of IKVM?
Many thanks,
Andy.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was wondering what are the reasons for IKVM preventing usage of Drools.Net? (We are currently in about same situation as you are)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2007-06-18
1. IKVM is an early beta 0.x.x.x - therefore Drools.Net will be in beta until that is sorted out. This then adds the complexity of potential issues. E.g. Is the issue in the Drools.Net port, or the underlying IKVM? How long would a fix in the IKVM take etc.. Basically it is a very big risk, as a lot of reliance is placed on a C# implementation of the JVM!
2. It must be an immediate performance hit.
3. The footprint for the rule engine becomes fairly huge @23.5mb. Compare this to NxBRE <500kb. We currently support 30k + users, so there is a fair emphasis on keeping app size small.
Hope that helps,
Andy
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What are the reasons for porting drools to .Net using IKVM? We are considering using Drools.Net in a project, but the use of IKVM is preventing this. One approach may be for us to port the entire codebase to .Net and submit back to the community. Are there some fundamental issues that force the use of IKVM?
Many thanks,
Andy.
I was wondering what are the reasons for IKVM preventing usage of Drools.Net? (We are currently in about same situation as you are)
1. IKVM is an early beta 0.x.x.x - therefore Drools.Net will be in beta until that is sorted out. This then adds the complexity of potential issues. E.g. Is the issue in the Drools.Net port, or the underlying IKVM? How long would a fix in the IKVM take etc.. Basically it is a very big risk, as a lot of reliance is placed on a C# implementation of the JVM!
2. It must be an immediate performance hit.
3. The footprint for the rule engine becomes fairly huge @23.5mb. Compare this to NxBRE <500kb. We currently support 30k + users, so there is a fair emphasis on keeping app size small.
Hope that helps,
Andy