Closed
Separate rulesets for each integrations?
Had few questions for you guys. Need architectural recommendation.
When it comes to connecting to external APIs (e.g. REST, SOAP, JMS) that our Pega Application plan to consume:
- Does Pega recommend creating separate rulesets for each integrations?
Show More
Had few questions for you guys. Need architectural recommendation.
When it comes to connecting to external APIs (e.g. REST, SOAP, JMS) that our Pega Application plan to consume:
- Does Pega recommend creating separate rulesets for each integrations? Or, use a single rulset that will contain Integration rules/components from many different interfaces?
- What are the pros and cons?
- What is the impact on rule resolution and performance?
- What if the number of interfaces/Integrations is high (e.g. 50)?
- What is the highest number of rulesets that you recommend to use in Application Stack?
Thanks,
Niaz
Show Less
Posted: 5 years ago
Decision Consultant Solutions
Decision Consultant Solutions
GB
Maintaining integration rules in separate rulesets helps in reusability of those rules in different applications. This improves the maintainability as well.
For example, You can create Org level, Div level integration rulesets and use them according to the layer and scope of the integration rules. You can group all the organization level integration level rulesets into OrgInt ruleset.
If the number of integration rules are very high then you can think of dividing them or grouping them into separate rulesets.