Posted: 30 Oct 2017 3:59 EDT Last activity: 23 Nov 2017 18:58 EST
[PEGA 7.1.6] High Availability Concerns For High Volume Applications
Can I get your assistance listing out the main concerns with configuring a high volume application for high availability?
The two I can think of, as of now, are the size of the common storage, whether file or DB, that would be required to store all requestor sessions. The other concern is the I/O resources monopolized to constantly write the updated requestor session to the file/DB.
I know quiesce of requestor sessions can be done explicitly in SMA. What is the automated way in which to trigger quiesce of each requestor so that any uncontrolled outage will not disrupt the user experience? What is the OOTB interval between refreshes of a requestor session to the shared file/DB?