This project aims at re-design the drools overall framework. By itself it has to be considered as a to-be-thrown PoC: as soon as a good design has been achieved and agreed upon, such design should be iteratively introduced inside drools repository.

The main focus of this project is on:

1. clear separation between "container" and "content" contexts; the "content" is represented by functionalities exposed by the compile-time and runtime; the "context" is the environment in which such functionalities are invoked ( see architectural choices for more details)
2. clear separation between compile-time and runtime
3. uniform overall management of different models/engines

Regarding the overall module organization/relationship, this project should follow the guidelines of the "Clean Architecture" principle. As per the design style, the microkernel-style will be featured, where each model/engine will represent a specific plugin.

Each plugin should provide a compilation and a runtime component.

That brainstorm page will be used as a place to share idea, suggestions, notes, while the refactoring proposal will be used to show technical diagrams.

The most important decisions (reason and choice) will be documented here.

The documentation folder contains diagrams (PUML, Archimate), images, and other resources related to design/architectural choices.

This effort can not be full-filled by a single person, since it involve decisions at every level and it will have an impact on the all drools codebase; everyone may be interested will be warmly welcomed for ideas, suggestions, criticism, contribution.

ArchUnit has been introduced to enforce (as much as possible) some general architectural and design guidelines.

See official documentation and maven plugin information for further details.