gitgabrio commented on PR #2065: URL: https://github.com/apache/incubator-kie-kogito-examples/pull/2065#issuecomment-2630962874
Hi @domhanak , thanks for the PR. Unfortunately, I'm afraid we are still lacking a sort of unified and consistent vocabulary. This sentence -> > This repository contains a number of examples for [Drools](https://github.com/apache/incubator-kie-drools), [jBPM](https://www.jbpm.org), [Kogito](https://github.com/apache/incubator-kie-kogito-runtimes) and [Sonataflow](https://sonataflow.org) that you can take a look at and try out yourself. Please take a look at the readme of each individual example for more details on how the example works and how to run it yourself. mixes different concepts as if they were the same. 1. _jBPM_ is a model, so it relates to an engine implementation, as _Sonataflow_ 2. on the other side, Kogito is a building / execution environment, that all examples are meant to feature 3. "drools" is a very ambiguous name, that may refer interchangeably to the rule engine, to all the engines inside the rools repo, or to the overall backend code in the above repo. All such confusion creeps around every now and then, even when interacting with other users, and also customers, and that makes harder to understand each other. I would like to propose the following terminology, and to start trying to adhere to that: > Engines: the unit of elaboration provided, i.e. the component that given a “model” (e.g. drl, dmn, pmml, bpmn) and an input, provide a result; Rules -> “drl” model; Processes -> “bpmn” model, others; Decisions -> “dmn” model; Predictions -> “pmml” model; Drools: the backend code (engines and glue-code) KieServer: the “old/first” environment developed where the functionalities have been originally developed and exposed; Kogito: the “new” environment that should expose the same functionalities Container: the environment providing functionalities to end user; it may be “Kogito” or “KieServer” I mentioned that years ago, when I was still part of the drools team, and IIRC it get approvals, at that time. I know someone would disagree a bit, especially the oldest members of the community, but I have the idea it better reflect our current architecture. wdyt ? Does this make sense ? @pibizza @mariofusco @baldimir @fjtirado FYI -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
