Drools & .NET Development

[Scott Morman]

I am curious to know if anyone here has attempted, looked into, or is currently developing against Drools but on the Microsoft stack. I understand that Drools is a Java-based system however there is a nice REST API that comes along with it. We are considering using Drools as our global product solution for a Business Rules Engine however we have both Java-based and .NET-based products that we develop. Java is obviously not going to be a concern because there are Java Client SDKs that are readily available. .NET is the concern. Yes, we know how to write code to communicate with REST-based services, that isn't the main concern. What is the concern in writing and supporting a .NET Client SDK where we need to manage the SDK over the long-term for things such as object mapping, creating the object model, and handling server upgrades that will cause backward compatibility problems.

I have been working on a POC to get a sense of what the development might look like for our engineers and I have been having some conversations with Red Hat to get their take on all this. So, I am curious about what others may or may not be doing. What has worked, what has not worked? Is it just better to find a .NET-based BRE instead of trying to consolidate on a single solution across both stacks?

Thanks for any help, insight, suggestions you all are willing to share.

Kind regards.

[Mark Proctor]

Should be fairly easy to setup your own json schema for your pojos on a rest end point, that any .net system can talk to.

Mark

--
You received this message because you are subscribed to the Google Groups "Drools Usage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drools-usage...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/drools-usage/0665904e-beb3-4421-927c-1223fbfa121b%40googlegroups.com.