For our load testing use-case, we have the following requirements/actors:
Issuer agent: this is the IDIM agent, hosted in OCP. We need to define whether we are going to be making requests directly to the agent, or through IDIM's controller. For the latter scenario, we need to define the integration points (APIs) and design new scripts for the load tester to be able to invoke those.
Mediator: our mediator instance, hosted in OCP. We will just need an invite URL to be injected as configuration into the tester.
Mobile wallets: spawned by the load tester, set-up to AT LEAST meet the rates described here.
Being able to track timing trends for issuance and verification (max/min/avg): is this supported in the tool?
The load tester will NOT be hosted in OCP, but rather in AWS or a dedicated server environment.
While we define the integration path and hosting location for the tester, focusing on the issuer agent integration and changes required to the load testing tool would be probably the best path forward.
Development can be completed against the IDIM SIT agent, test executions will be run against a pre-production environment.
esune
commented
5 months ago
For our load testing use-case, we have the following requirements/actors:
The load tester will NOT be hosted in OCP, but rather in AWS or a dedicated server environment.
While we define the integration path and hosting location for the tester, focusing on the issuer agent integration and changes required to the load testing tool would be probably the best path forward.
Development can be completed against the IDIM SIT agent, test executions will be run against a pre-production environment.