Tom Zhang (ZHANQ)
Principal System Architect
Pegasystems Inc.
ZHANQ Member since 2007 5 posts
Posted: March 21, 2017
Last activity: March 28, 2017
Posted: 21 Mar 2017 15:37 EDT
Last activity: 28 Mar 2017 8:23 EDT

Multiple PRPC applications share the same PRPC database instance.

I understand PRPC in general support multiple applications sharing the same PRPC rule base. But Is this the recommendable approach for enterprise application ?

I can see there are some overhead or restrictions in this approach

1. For SSO, if one user access multiple application, user might end up in wrong application and has to manually switch applications.

2. Overhead in separating assignments, queue items, attachment links among shared tables.

3. Overhead in purge and archiving.

3. Performance, sometime core application in production can be impacted by other shared applications.

4. Individual application production migration and upgrade

5. AES monitoring, need to separate production diagnostic for each application.

What is Pega stand on this approach ? Any other pros and cons in this approach ?

Many Thanks !!


***Updated by moderator: Lochan to add Categories***

Low-Code App Development Data Integration System Administration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.