Creating dedicated runtime pods for specific rulesets

You use this feature to create dedicated runtime pods for specific rulesets, and define paths that route the rulesets to the pods. This configuration provides greater isolation, improved scalability, and optimized performance for your decision service deployments. You get fine-grained control over resource allocation and configuration.

When you implement the dedicated runtime pod feature, the regular Decision Server Runtime pods and services are still created. Any requests with paths that do not go to the dedicated runtimes are automatically directed to the default Decision Server Runtime. This arrangement ensures that all the requests are properly handled. The dedicated pods manage configured paths, and the default pod handles the rest of the traffic.

Benefits

Isolation

• Independent operation: Each RuleApp or ruleset operates in its own dedicated environment.
• Enhanced stability: Reduces conflicts between rulesets that share resources.
• Failure containment: Issues in one ruleset do not affect other rulesets.

Scalability and performance

• Resource optimization: Tailor CPU and memory allocation based on the requirements of each RuleApp or ruleset.
• Improved efficiency: Optimize resource usage for different types of decision services.
• Workload prioritization: Allocate more resources to business-critical rulesets.