Currently we are running our application in PEGA 7.4 and planning to uplift to PEGA 8.8 end of 2023. Also our current DB setup is Active-Passive. We are looking for options to improve the application availability as there might be scheduled outage on server patching or PEGA version upgrade or any other. Does Pega 8.8 supports Active-Active DB setup ? If so any guidance / support instruction and what is the criteria of the work type to accomodate Active Active.
Note: out application cases are 90% straight through to resolution, but some of them worked on by users manually by workflows and cases are persisted in the DB.
Pega supports active, passive database connections. As long as you point to load balancer of the database, database connection requests will fall back to passive database when ever active is down.
@SriHarsha Anika . Thanks for response. Yes, we are currently setup as Active-Passive as you defined. Could you please clarify if PEGA also supports Active-Active if so any precondition to be met w.r.t. case type/flow/retention perspective ?
you have to handle it outside of Pega through your database vendor.
Vendor is responsible for replicating data into 2 databases and synchronizing data as required for backup/recovery etc. needs. As such if this needs to be handled from application it will severely degrade application performance.
That’s not a software practice to insert same record into 2 databases (one is replica of another) in single transaction from an application . Such CRUD operations has lot of racing conditions with respect to locking, synch etc..
Data consistency cannot be guaranteed in this approach.
It is not supported and that’s not a software architecture practice too which can be supported in any version.