We performed a comparison between Apache JMeter and Apigee based on real PeerSpot user reviews.
Find out in this report how the two API Testing Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The reports and analysis tools are very good. They are the solution's most valuable features."
"Apache JMeter is quite flexible."
"Due to process automation, I don't have to prepare reports, making it the perfect solution."
"When there's a high number of TPS I can achieve more transactions per seconds given the hyper-limitations."
"It's a powerful tool that is open source."
"JMeter is a free tool with a large user population, which comes in handy because we have a vast knowledge base to tap into when needed. It's also easier to hire consultants who know JMeter."
"This solution is very user-friendly, and allows for a lot of data capture when testing."
"The most valuable feature of this solution is being able to launch many requests and scheduling simulating human interactions with the application."
"They capture the details of all the incoming and outgoing traffic of your APIs. Based on 300+ default dimensions you can generate beautiful and insightful reports on usage and consumption of APIs."
"The most valuable feature is monetization."
"The solution is stable and reliable."
"Items around the mobilization of the API interface and the ability to automate validations for our APIs are the most valuable aspects."
"The most valuable feature is the API gateway."
"Great flexibility with its features."
"We have been using Apigee mostly for proxy FGIs. We also use its security features as well as traffic control features."
"The pricing is okay."
"Until now, JMeter is not supporting most of the protocols."
"There are certain things like we can't merge custom metrics into the JMeter reports. We're limited to JMeter metrics, and other server metrics can't be integrated with JMeter dashboard. This forces us to rely on another tool."
"The interface could be made more user-friendly."
"Because so much is being done these days with authentication processes, a better system for either getting bearer tokens or some kind of token-based authentication prior to executing APIs would benefit the product. It is there, and you can do things. It is just not real clean at this point. There should be a better authentication process for JMeter or some automation or better guidelines for gaining and utilizing tokens on the fly."
"The installation needs some work. It could be simplified."
"Given that Apache JMeter is a free and open-source tool, documentation improvement may not be a major concern, as it is mostly contributed on a voluntary basis. The essential information is already available. However, in terms of the interface, there are occasional bugs, and the tool may not address them as quickly as some users would like. Fixing defects and bugs might take a considerable amount of time, with users sometimes having to wait for several months or even a year for the next release to address specific issues."
"Currently, the integration pipeline is implemented by using Jenkins or a similar tool platform. These are continuous integration tools. As far as I know, integration is done by using custom scripts. It would be good if the integration with a continuous integration pipeline, like Jenkins or Hudson, can be done out of the box without using a script."
"It has some proxy-based dependencies which require specific proxies to be set up or disabled, which causes problems."
"One feature they have to invest time into is the developer portal they use."
"Proxy versioning seems a bit confusing/buried in the publishing experience, especially for the URI-based versioning approach."
"I would recommend this solution to those who want to start using it, but it depends on the requirements and automation."
"Access restrictions can be improved."
"The entire user across all the layers should be singly authenticated through an external authentication system."
"What my clients don't like is that the on-premises solution is not being treated and maintained as well as the cloud solution."
"I would like to see SOAP services and socket-based connectivity developed."
"Apigee on premise is quite complex and it is always moving faster."
Apache JMeter is ranked 3rd in API Testing Tools with 82 reviews while Apigee is ranked 6th in API Testing Tools with 82 reviews. Apache JMeter is rated 7.8, while Apigee is rated 8.2. The top reviewer of Apache JMeter writes "It's a free tool with a vast knowledge base, but the reporting is lackluster, and it has a steep learning curve". On the other hand, the top reviewer of Apigee writes "Has a robust community and outstanding performance". Apache JMeter is most compared with BlazeMeter, Postman, Tricentis NeoLoad, Katalon Studio and OpenText LoadRunner Professional, whereas Apigee is most compared with Microsoft Azure API Management, IBM API Connect, Amazon API Gateway, WSO2 API Manager and Layer7 API Management. See our Apache JMeter vs. Apigee report.
See our list of best API Testing Tools vendors.
We monitor all API Testing Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.