Question
HCL Technologies Ltd
IN
Last activity: 30 Sep 2024 7:15 EDT
Regarding AWS Database Instance
Hi Team,
We are currently in the process of migrating RPA from current client to a new client since the business itself is getting migrated. Our query is that currently we have Oracle in house DB as backend for Pega Platform , but for the new client we need the AWS DB requirements for the procurement. Currently our Pega RPA is being used by about 250 users 8 hrs. per day; which is the general average for about 11 months but during a business critical, high volume month these users increase upto about 750. Can anyone help us in estimating the CPU RAM and Storage requirements ?
Regards,
Mahesh
Accepted Solution
Updated: 30 Sep 2024 7:15 EDT
Pegasystems Inc.
GB
Updated: 10 Sep 2024 10:21 EDT
Pegasystems Inc.
GB
@MaheshwarA please have a look at a similar question here:
How to know hardware sizing since Pega stopped hardware sizing estimate service
Note that there is a "Architecture & Infrastructure Modernization" (AIM) Service to help size and manage the migration from VM to K8s deployments offered to our Client Managed Cloud deployment clients - they can request a sandbox on the cloud topology of their choice. There is also a Load Testing Services which is a Standard offerings out of Consulting.
We do not offer a hardware estimation service currently as the old VM based deployments are legacy. We urge users to migrate to K8 whether on prem or customer cloud.
@ tomas is there a Robotics-perspective on this question? @Angel Hermira is there something you could contribute on this question?
Accepted Solution
Updated: 30 Sep 2024 7:15 EDT
Pegasystems Inc.
GB
@MaheshwarA , for the sizing question. Based on the volumes you mentioned, you can go for the same that you have today which is likely to be the minimum Pega Platform requirements. The DB size and performance should be replicated in your new choice.
However, if you don't have noticed, AWS DB is not a supported DB for Pega Platform https://docs.pega.com/bundle/platform/page/platform/deployment/platform-support-guide/platform-support-guide.html at the moment. You may need to go for PostgreSQL or Oracle in your new container.
@MaheshwarA , for the sizing question. Based on the volumes you mentioned, you can go for the same that you have today which is likely to be the minimum Pega Platform requirements. The DB size and performance should be replicated in your new choice.
However, if you don't have noticed, AWS DB is not a supported DB for Pega Platform https://docs.pega.com/bundle/platform/page/platform/deployment/platform-support-guide/platform-support-guide.html at the moment. You may need to go for PostgreSQL or Oracle in your new container.