Architectural technical debt is a design or construction approach that's expedient in the short term, but that creates a technical context in which the same work requires architectural rework and costs more to do later than it would cost to do now (including increased cost over time).
Efesto initiative was meant to unify them behind a common, unified API, that would allow
better abstraction for client-code (e.g. kogito-runtimes -> engines
easy integration of new "engines" (completely new engines or different implementations, e.g. TrustyPMML and jPMML)
OOTB engine integration
single-place for new cross-boundary features (e.g. messaging, monitoring, etc)
Currently, fully supported engines are DRL and PMML.
DMN is ongoping work.
BPMN/SWF to evaluate
Different engines uses functionally-equivalent method to achieve same behavior (code-generation, model execution).
This is an Architectural Technical Debt.) :
Architectural technical debt is a design or construction approach that's expedient in the short term, but that creates a technical context in which the same work requires architectural rework and costs more to do later than it would cost to do now (including increased cost over time).
Efesto initiative was meant to unify them behind a common, unified API, that would allow