Layer7 API Security vs. IBM DevOps Test Performance

Well suited for publishing internal services with very high security, protecting against attacks, and managing on-demand load. Also good for transform messages and SQL to Rest services. Not appropriate for business logic implementation.

Incentivized

Go for IBM RPT if: 1. You're testing a Java-based Web application with HTTP protocol 2. You wanted to distribute the load across machines easily 3. Your team is in learning phase/not really introduced to a wide range of performance testing tools Do not go for IBM RPT if: 1. You wanted to test REST or any other advanced protocols 2. Your system under test demands a very high user load 3. Your application is written in .NET or any other platform except Java.

Incentivized

• SOAP to Rest / Rest to SOAP web services transformation.
• Secure authorization and authetication (JWT, OpenIP Connect, OAuth, SAML and more). WASP Features as injection protection.
• Easy rule writing without coding.

Incentivized

• Data Parameterisation/ Data Correlation is made simpler compared to its competitors
• Distributed Load Testing is easier to set up
• Performance metric gathering while a test is in progress
• Th look and Feel really helps a beginner to understand and work with.

Incentivized

• It would be nice to have an integration with services like Github for managing projects and versions.

Incentivized

• Memory utilization could have been improved.(Eats up system's RAM)! It may crash if a test is conducted with the heavy load if adequate RAM is not available in the VM/host machine.
• Licensing could have been made simpler. IBM's licensing method is difficult to follow.
• Support for protocols other than HTTP. Not really up to the current trend.

Incentivized

The Layer7 API Management is a great solution, but, sometimes the documentation is not clear or has lack of examples.

Incentivized

The support team is good and the response time is reasonable, but (there is always a but), when support inquiries are made by someone experienced, and the question is not trivial, it is boring and takes a long time to get the case escalated to the next level of support.

Incentivized

We evaluated 3 tools and decided on Layer7 API Management because it had the shortest implementation times and fastest learning curve, without losing power of customization and scalability.

Incentivized

Cost/Licensing: While JMeter is an opensource testing tool from Apache, compared to IBM RPT and HP LoadRunner, RPT is much cheaper than Loadrunner. Functionality: JMeter provides basic functionalities which are adequate for performance testing, however advanced features are not available (such as load testing with GUI, reporting is very basic etc.). But when it comes to Loadrunner, it offers very broad features and supports a variety of protocols. So in this category, Loadrunner is a winner, but RPT is better than JMeter. Ease of operating: JMeter is easy compared to LoadRunner, but it has old GUI and look and feel is not that great to understand. Also, most of the things are to be done in a command line, non-GUI mode. While LoadRunner is very advanced with many options, which also confusing sometimes. But RPT, on the other hand, maintains a balance between simplicity and offering of different features. So winner: RPT.

Incentivized

• Very fast implementation and is easy to learn & use.

Incentivized

• Accuracy in metrics, thus improving system's performance
• Costs less compared to competitor like HP LoadRunner
• Helped the team of beginners learn things quickly

Incentivized