JMeter for performance and load testing.
Use Cases and Deployment Scope
JMeter is used predominantly for performance and load testing purposes. As our application stack is majorly microservice-based, thousands of APIs are developed, enhanced, and maintained to enable a satisfied customer experience. To achieve this, the APIs should meet the expected performance metrics, and JMeter helps in validating them through our SDLC release cycles.
Pros
- All kinds of response formats are supported.
- JMS or message based systems can also be tested seamlessly.
- Pluggable samplers, visualization tools are helpful.
- Open source and free.
Cons
- JMeter's UI or frontend can be improved to be more lightweight.
- Not ideal for user based performance testing, since no support for final rendering.
- System resource-intensive.
Return on Investment
- Positive impact in meeting the NFRs.
- Stable tool.
- Easily integrated into SDLC process pipelines.
Usability
Alternatives Considered
BlazeMeter
Other Software Used
Apache Kafka, Red Hat OpenShift, Apigee Edge, Splunk AppDynamics, Splunk Observability Cloud, Glassbox, LiSA, GitHub Copilot, GitHub, IntelliJ IDEA

