| ILOG JRules User Guide > Creating Rule Projects > Concepts > Rule Project > Guidelines for Defining an Architecture for Large Rule Projects |
Guidelines for Defining an Architecture for Large Rule Projects |
PREVIOUS NEXT |
When your rule projects grow larger, you can usually improve Rule Studio performance by reorganizing the architecture of your business rule application.
Rule projects can grow into two directions:
In Rule Studio, many operations are carried out at the rule project level, such as build, queries, refactoring, and ruleset extraction. Other operations, such as Content Assist and debugging, require browsing through all the rule project items. If you have a large number of rule artifacts in your rule project, these operations become slower.
To avoid having to manage a large number of rule artifacts in your projects, you can try to break down your application into several rule projects, which must then reference each other.
With this modular organization, you work with the set of business rules 1 artifacts separately from the set of business rules 2 artifacts.
Rule Studio performs better with this modular organization.
Rule Studio is usually more efficient when you work with several small or medium sized packages, as opposed to a few large packages. The reasons for this are:
However, make sure that you do not have too many small packages, because it slows down Rule Studio in finding rule model elements.
When your rule project contains a large business object model, business rule language-related features are slower. Parsing, checking, Content Assist, and navigation in business rules and technical rules is slower with large business object models.
If a set of rules uses only a part of the business object model, you can consider isolating the set of rules and the part of the business object model into a separate rule project. Thus, when you work with the rules, you have visibility only on the adequate BOM classes.
You can also split a large BOM entry into several smaller ones for more flexibility.
When you define a BOM entry from a XOM, the BOM entry may include a lot of technical classes and methods that are not actually used in your rules. Because the size of the BOM has an impact on Rule Studio performance, we recommend that you remove all unused business elements from the BOM.
When you work with a very large business object model, the completion boxes in the Text and Guided editors can become quite large. This can be both a usability and a performance issue. To reduce the number of the completion entries, and to make them more relevant to your rules, you can use categories. Categories are a good way to organize your vocabulary into subsets.
| Copyright © 1987-2008 ILOG S.A. All rights reserved. Legal terms. Documentation homepage. | PREVIOUS NEXT |