How to save dynamic facts into database about json-rules-engine HOT 5 CLOSED

@arsalans Would you mind elaborating on why you need to persist actual code? The library is designed with the intention that you won't need to do this. The idea is that you save the rule.toJSON() results into the database, and hydrate a new engine instance when they are later later retrieved.

The fact definitions themselves should remain in code-land, and shouldn't ever need to be persisted.

from json-rules-engine.

@CacheControl So I created two micro-services, one creates the rules and facts and saves them into the database, the other one consumes them. With this limitation of not saving methods in Json (not by the engine btw), I may have to merge both of them into one.

from json-rules-engine.

@arsalans If the first microservice is just providing rule CRUD, why does it need to know about the facts? Why not just have the runner service have the fact definitions?

In case I'm missing something and this is necessary, an alternative to merging the services would be to move the fact definitions into a private npm package and install it into both services.

from json-rules-engine.

from json-rules-engine.

Great, I'll close this for now but feel free to reopen if there are any surprises

from json-rules-engine.