Evaluating Infrastructure for High-Traffic API

Hello,
We have an API expected to handle traffic between 700K and 1M requests per day. Our current production platform hardware configuration is as follows:

APIGEE Platform: 4.53.0

S.No. Components CPU RAM Storage

1 MS, CS ZK 8 16 GB 250 GB
2 CS ZK 8 16 GB 250 GB
3 CS ZK 8 16 GB 250 GB
4 RMP 8 16 GB 100 GB
5 RMP 8 16 GB 100 GB
6 QS 4 8 GB 50 GB
7 QS 4 8 GB 50 GB
8 PS 8 16 GB 500 GB
9 PS 8 16 GB 500 GB
  1. Can this infrastructure handle the anticipated traffic volume smoothly?
  2. Do you have any recommendations or best practices to ensure integration remains smooth and highly available under such high traffic?

Hi @dchiesa1 , your input on the above case would be greatly appreciated!

Hi @Roaa_APIGEE , What is the anticipated TPS for the environment? where are the apigee VMs deployed ?

Also the best way to understand if the infrastructure is able to API traffic is to run a distributed load test on it and analyze the results. Load testing tool like apache jmeter can be used.