Rule Management Hybrid

Using the Catalog only in Development for the Rule Development Life Cycle

• The Catalog is used in development and the file system is used for rules in other environments
• Only one Catalog web service and database instance is required, for use by the development environment
• Rule changes can be propagated by downloading rules from the catalog web service and then saving to the file system in other environments
• Multiple rule authors can edit the same rule application concurrently
• Rule changes can be hot-deployed from the production file system without restarting production application
• Production application is not dependent on stability of the Catalog web service and database
• Audit trail for rule changes is only available in development
• A simple, custom-coded component may be required for integration with automated build processes or continuous integration