We just raised a $30M Series A: Read our story

Micro Focus LoadRunner Cloud OverviewUNIXBusinessApplication

Micro Focus LoadRunner Cloud is #4 ranked solution in top Performance Testing Tools and top Load Testing Tools. IT Central Station users give Micro Focus LoadRunner Cloud an average rating of 8 out of 10. Micro Focus LoadRunner Cloud is most commonly compared to Micro Focus LoadRunner Enterprise:Micro Focus LoadRunner Cloud vs Micro Focus LoadRunner Enterprise. The top industry researching this solution are professionals from a computer software company, accounting for 33% of all views.
What is Micro Focus LoadRunner Cloud?

Micro Focus LoadRunner Cloud is a simple, smart and scalable cloud-based load and performance testing solution for agile and DevOps teams. It helps you to detect performance issues and ensure that your mobile and web apps are ready for the load. It provides an Intelligent and predictive analytics for fast problem detection and scale up to millions of user in minutes from different regions.

Micro Focus LoadRunner Cloud was previously known as StormRunner Load, LoadRunner Cloud, and Micro Focus StormRunner Load.

Micro Focus LoadRunner Cloud Buyer's Guide

Download the Micro Focus LoadRunner Cloud Buyer's Guide including reviews and more. Updated: November 2021

Micro Focus LoadRunner Cloud Customers

Alfa Bank, N Brown Group, University of Copenhagen, McGraw-Hill, Cognizant

Micro Focus LoadRunner Cloud Video

Pricing Advice

What users are saying about Micro Focus LoadRunner Cloud pricing:
  • "We make use of virtual user hours. We buy time in the LoadRunner Cloud. It costs around $80,000."
  • "There is no monthly or yearly cost but rather, the fees are based on the amount of traffic that you use."

Micro Focus LoadRunner Cloud Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Michael Daniel
Sr. Technical Test Analyst at a educational organization with 1,001-5,000 employees
Real User
Top 20
Enabled us to eliminate load generators, and automatically triggers and produces reports

Pros and Cons

  • "The fact that the solution supports multiple protocols such as open source, VuGen, TruWeb, TruClient, and SAP is very important because these protocols help us to concentrate on what is really needed to produce performance tests. If something is not supported, you have to use other tools or find other ways of assimilating loads."
  • "We are trying to put it into a complete CI/CD pipeline, but there are still some challenges when you try to run it through different protocols. The challenges are around how you can containerize applications. There are some limitations to some protocols, such as desktop. And when it comes to database testing, there are some things that we can't do through CI/CD."

What is our primary use case?

I have been using it to analyze the performance of various enterprise systems like SAP, web applications, Oracle Labs, and mobile app applications as well. The objective of the performance testing is to assess the system and whether it can withstand an actual load.

How has it helped my organization?

One of the main benefits is that we don't need to worry about load generators. Before we had Loadrunner Cloud, we had 10 to 20 load generators, and we needed to maintain them. There were always upgrades. We would also have to configure the load generators when we were ready to test, and at times there was stuff to clean up. None of that is necessary anymore. We can concentrate most of our time on creating scripts and configuring Loadrunner based on our objectives. It's very easy for us. We don't need to worry about what happens in the backend or how the load is distributed.

A second advantage is the reporting system. Once a test is done, even if it's in continuous integration and continuous delivery, it automatically triggers and produces reports. We can send the reports to multiple dev teams whose developers are expecting the reports.

Another advantage of the solution is seen compared to others we have used, like JMeter, and IBM solutions. LoadRunner has reduced a lot of the time involved in the scripting cycle because of TruClient. We only need to record one time and we can configure it accordingly to create various scenarios. It has reduced scripting time by about 50 to 60 percent.

When we do mobile applications, every build can be tested with LoadRunner Cloud. Once the developer checks into a particular branch, we call it a mod branch, the performance test is already integrated into it. They can trigger it through their continuous pipeline. For mobile development platforms, it's very crucial because notifications and other things need to be tested before we send to prod. Notifications are very load-sensitive because they go to every user—it could be 10,000 or 20,000 users—and we previously had issues with this. Using LoadRunner Developer and continuous integration has helped us.

What is most valuable?

Recently I have found the TruClient tool to be very useful. My team is involved in a lot of performance testing of applications including mobile platforms and different types of web browsers. In those cases, LoadRunner TruClient is very crucial to testing the performance. TruClient is one of the best features, one I use every day to create load scenarios.

The fact that the solution supports multiple protocols such as open source, VuGen, TruWeb, TruClient, and SAP is very important because these protocols help us to concentrate on what is really needed to produce performance tests. If something is not supported, you have to use other tools or find other ways of assimilating loads. For example, when you are trying to create loads for web applications, if it's not TruClient, you need to find and analyze every call: What the HTTP request is, and what the other kinds of requests are that we need to call, and then correlate all the correlation identifiers. All of that is taken care of by TruClient and other protocols. That is actually very beneficial across all the platforms. For example, a SAP application might be tested for mobile. We can use a combination of the SAP protocol and TruClient protocol. The combinations are very helpful for performance testing.

LoadRunner Cloud gives you a lot of options, even for multi-browser or multi-device testing. It has been the main tool that can do everything; complete end-to-end performance testing.

The support for large-scale testing is also an important feature in our operations. We have thousands of users and it provides the best solution. You can have an unlimited number of users, although you would need to pay for them, but that's a different story. In our organization, the maximum number of users is currently about 20,000 to 30,000. It's a one-stop solution. I can configure my load on the cloud environment and have 30,000 virtual users on the cloud. I don't need to create the infrastructure locally and I don't have to maintain it. Everything is taken care of by the solution.

In addition, its ability to run unlimited concurrent tests without worrying about hardware availability helps eliminate hardware dependency. You don't need to have the load generators on your network. You don't need to maintain those systems and you don't need to have that kind of network capability. If you're testing on-prem, but you don't have the network capacity to scale up to millions of users, LoadRunner Cloud enables you to create virtual networks and use the cloud to generate those kinds of loads. You can then analyze what the impact will be to your system when you have millions of users. LoadRunner Cloud is the best way to do that.

What needs improvement?

When it comes to the CI pipeline, there were some limitations initially, but the latest version of LoadRunner is very helpful. They can integrate into the CI/CD pipeline. We are trying to put it into a complete CI/CD pipeline, but there are still some challenges when you try to run it through different protocols. The challenges are around how you can containerize applications. There are some limitations to some protocols, such as desktop. And when it comes to database testing, there are some things that we can't do through CI/CD.

For CI/CD, the previous versions may not be the right ones, but the latest version is definitely a step ahead. We are aiming for 100 percent, but we have achieved around 60 to 70 percent in CI/CD. Still, it's very good to have that capability.

Also, it would be helpful if Loadrunner Cloud had the same kind of enterprise environment where we had multiple models and options while creating the load profile. Not all the options are available in the LoadRunner Cloud. If they could be added, it would be good.

For how long have I used the solution?

I've been using a LoadRunner solution for more than 10 years as part of my performance testing.

What do I think about the scalability of the solution?

The efficiency of the scalability is a 10 out of 10. I have used multiple tools and LoadRunner is the best one in terms of efficiency. When it comes to cost-effectiveness of the scalability, I would give it an eight out of 10. Even though it's cloud, and you can have thousands of users, we are paying in the tens of thousands. It's not so cost-effective for a university like ours. We still have to justify why we need to spend so much money every financial year.

How are customer service and technical support?

I have used Micro Focus technical support a couple of times and they have been very supportive. They're good.

How was the initial setup?

The only problem with setup is that there might be some problems with the firewalls, configuring SSH and other things. We were initially using Micro Focus SiteScope but we had some issues getting all the metrics. With New Relic and Dynatrace, we stopped using SiteScope. Other than that, we didn't have any issues. It's pretty straightforward. You install LoadRunner, configure your virtual users, and create the environment.

Our initial deployment of the on-prem solution took a week to get everything done, including setting up the firewall, configuration files, and the protocols. The migration to Loadrunner Cloud is nothing. You can start triggering whatever code you had on-prem in the cloud. There really isn't any migration involved. It's pretty straightforward.

What was our ROI?

We have definitely seen return on our investment with Loadrunner Cloud. As I noted, we used to have many load generators and they are no longer used. That is saving us about $30,000. And Loadrunner costs 50 percent of what it used to cost us to run the same test in the cloud. We don't need a Windows Server license anymore or networking capabilities specifically for testing. Those are the kinds of savings we have seen from moving to the cloud.

Also, in the past, we used to write code. But with TruClient, while you need a performance tester, you don't need a programmer to write scripting. If you know the system, and if you know the objectives of performance testing, you can do the performance tests. No programming skills are needed. That also gives us leverage. We can use someone with performance testing capabilities, even though he might not be the best programmer. That has also reduced our costs by $10,000 a year.

Which other solutions did I evaluate?

I have extensively used JMeter as a performance testing tool. JMeter is free and also enables codeless scripting. Even without coding you can try running scripts. But where there is no comparison between JMeter and LoadRunner is when it comes to distributing load. LoadRunner stands out. With JMeter, it's very difficult to distribute the load. 

When it comes to creating reports, Loadrunner is best. You will spend most of your time analyzing what's happened with the test, analyzing bottlenecks and pain points with the performance parameters. But in JMeter, you have to manually collect everything: collate the results and produce the reports. Then you need to do a detailed analysis to find the bottlenecks and resource patterns. It is very difficult, but it's free. If you have the skill set and the time, you can use JMeter. But if you are time-constrained, and you want to actually concentrate on performance testing, use LoadRunner.

LoadRunner Cloud provides application performance and management tools to an extent, but not to the extent of New Relic or Splunk. We predominantly use New Relic to monitor application performance and in some cases we use Dynatrace as well. But LoadRunner Cloud doesn't have complete application performance monitoring metrics.

What other advice do I have?

LoadRunner's Developer integration enables developers to script and run tests without leaving the developer ecosystem. It gives a complete IDE where you can develop the code and add your script. For example, if you are using a Java platform to code, and it has all the libraries and the IDE, you can integrate your load testing into your development. For us, because we don't have a single development cycle or ecosystem—we constantly move to various methods—that's where the IDE has limitations. It supports certain languages but it doesn't support everything. If we are using Go, for example, we might need to add certain libraries, so that's where it isn't helpful. But if you are purely on Java or core platforms, it will definitely help.

The Developer integration enables developers to add performance testing to their day-to-day tasks, but shift-left depends on your company's development strategy. If your whole culture supports shift-left, so that your quality assurance is embedded from the start of the development cycle, then shift-left works out. But in our case, we use a lot of packaged applications like Workday or SAP where we don't have much opportunity to work with their code. We do a lot of configurations and integrations. In that case, shift-left doesn't work as well. But whether you follow shift-left or shift-right, Loadrunner Cloud works.

For non-functional testing, LoadRunner is the best tool. I can recommend it to other people, to create specific tests from the smallest load to the highest level of load. I don't think any other commercial tool has that capability to create load performance testing. There is no other tool that gives this kind of experience for a load-testing professional. From end-to-end, starting from creating the load scenarios, to running them, and then reporting, LoadRunner is the best tool. You save a lot of time and, with LoadRunner Cloud, you are saving a lot of money. Go for it.

Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Flag as inappropriate
Abbasi Poonawala
Vice President Derivatives Ops IT at a financial services firm with 10,001+ employees
Real User
Top 5Leaderboard
Offers good record and playback and endurance features

Pros and Cons

  • "The record and playback feature is the most valuable feature. It's all driven by the script, so it's a script-based tool where the background tracing starts. Java's background process does a lot of tracing. The process starts in the background. It sees what peaks of volumes that the process can handle. It's easy to use because it's script based, record, and playback. I"
  • "I would like for there to be better integration with other tools so that when you do load testing you can also do a security check."

What is our primary use case?

It is all about load testing. We have to do a lot of load testing in our IT environment. In the investment banking space, you do a lot of end-to-end endurance testing, to see how to benchmark performance based on resources and the CPU memory. So, we will have to benchmark the performance based on trade volumes. Trade volumes are the basic KPI.

Endurance testing needs to be done to see how many trades can be pumped in my environment. I do endurance testing. 

What is most valuable?

The record and playback feature is the most valuable feature. It's all driven by the script, so it's a script-based tool where the background tracing starts. Java's background process does a lot of tracing. The process starts in the background. It sees what peaks of volumes the process can handle. It's easy to use because it's script based, record and playback. I play certain tests. I record those tests, see how they pass through the entire environment, and see how many breaks I get. 

Then we repeat that for multiple numbers. If the first time, I pumped in 1 million trades, and get 5% of the failures, then I try with 2 million trades and I see that there is a 7% failure. These scenarios are easy to do in the LoadRunner. LoadRunner has been the best tool for more than 20 years in the market.

You can do endurance testing, you can do load testing. These are the different types of load testing. It lets you see how much volume you can benchmark in your entire environment, given the resources like CPU and RAM. 

The record and playback is the best feature. You need to use a console. You log in to your console and see the dashboard with how many trades failed and how many trades passed, what the peak loads endurance load were. 

What needs improvement?

The performance has really improved in terms of running test cycles. The product used to crash on-premises and when it had a lot of trades being pumped in. Because it is memory intensive, it used to crash if it was running out of memory. That was the limitation of the on-premises thing. Running those states and cycles in the cloud is much faster. 

Everything is frozen in the cloud. The RAM, CPU, compute, and storage are provisioned in the cloud, which is becoming easier for running these test cycles. Test cycles are highly effective. Of course, you need to have a test strategy, like volume-based load testing. Configure some test cases and run those test cases in cycles. Cloud performance is much faster. Volume-based endurance testing is easier in the cloud.

For how long have I used the solution?

It is an old solution, around 20 years old. It was called once Mercury LoadRunner and then it was acquired by HP, it became HP QTP. That was around 2007, it was known as Hewlett-Packard HP QTP. Since then it has been acquired by Micro Focus.

What do I think about the stability of the solution?

It is very stable.

What do I think about the scalability of the solution?

We have around 100 users, they are functional experts who use this for load testing.

The people who have been responsible for setting the KPIs will decide if we will expand the solution. They are the end-users. It will depend on the dashboard and the results of the load testing.

How are customer service and technical support?

LoadRunner is a very old product in this industry. It was a little difficult to get to the right support team. Now there's a professional service group that is better than they were before. 

If scaling becomes a problem, then we have to involve the support, the right kind of support to actually fine-tune and troubleshoot the entire configuration. But with the cloud version, that risk is minimized. It has adequate storage available.

What's my experience with pricing, setup cost, and licensing?

It's a subscription-based, pay-per-user license. I wouldn't say it's expensive. 

Because it was an on-premise license, it was a costly affair. Only certain stakeholders could use it. Now, it is enterprise-wide, we can have any number of cloud users performing the load testing because it is pay-per-user.

What other advice do I have?

I would recommend LoadRunner. It is an industry-leading tool. You can benchmark the volumes on the dashboard and it is easy to use.

I would definitely recommend it for investment banks and certain businesses like OTC derivatives.

I would rate LoadRunner an eight out of ten. It has good documentation. The recording and playback scripts can be easily done. I would like for there to be better integration with other tools so that when you do load testing you can also do a security check.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Learn what your peers think about Micro Focus LoadRunner Cloud. Get advice and tips from experienced pros sharing their opinions. Updated: November 2021.
554,529 professionals have used our research since 2012.
Allan Beumer
Lead Performance Test Engineer at bol.com BV
Real User
Top 20
Enables us to performance test our warehouse management system for peak load

Pros and Cons

  • "The TruClient feature is the most valuable for us. An application with testing can only be scripted using TruClient, so it's part web-based, but it also has its own protocol combined with HTTP and HTML. So many other tools do not recognize this specific proprietary protocol. Using TruClient, we can still create scripts that cover everything that we need to cover."
  • "Reporting and analysis need improvement. Compared to the old school LoadRunner Windows application, the reporting and analysis are mediocre in LoadRunner Cloud."

What is our primary use case?

We use a warehouse management system, my company is like a Dutch Amazon. We use LoadRunner to performance test the warehouse management system for peak load. So if Valentine's Day, Christmas, or whatever comes up, we try to run all functional loads through LoadRunner Cloud and make sure the peak count can be handled by the WMS. We use it almost daily. We have peak periods where the testing will increase, but nowadays it's so busy that throughout the year, it's almost the same. It's the same high load every day and we're testing continuously.

The amount of load on the system wasn't that large a couple of years ago for us to test. So the business case for performance testing wasn't pointing to investing in it, but now we have such huge, increasing numbers and increasing load that it's worthwhile setting up a structured and automated performance test and to invest in something like LoadRunner Cloud.

We use the cloud. The controllers and the dashboard servers are in the Micro Focus cloud. But we use our own load generators, which are on-premise. So we use a hybrid setup.

How has it helped my organization?

Before LoadRunner, we weren't even testing performance and now we're performance testing. So we now do performance testing as part of the delivery of a new release, which is an improvement compared to a couple of years ago. 

What is most valuable?

The TruClient feature is the most valuable for us. An application with testing can only be scripted using TruClient, so it's part web-based, but it also has its own protocol combined with HTTP and HTML. So many other tools do not recognize this specific proprietary protocol. Using TruClient, we can still create scripts that cover everything that we need to cover.

It supports multiple protocols, which is important to us. We also use JMeter open source combined in LoadRunner Cloud. In our company, we also use open-source performance testing tools like JMeter, Gatling, and Locust. It's important to be able to embed those scripts as well into a LoadRunner-based performance test. So it would really help us to have a single place for all kinds of test scripts and the open-source ones.

It's also very important to us that LoadRunner allows full integration into the ACI pipeline. We were focusing on a shift left on not only functional testing but also performance testing. And we're trying to integrate the performance testing in our CI/CD pipelines currently. So the better it supports this, the better and easier it is for us.

What needs improvement?

Reporting and analysis need improvement. Compared to the old school LoadRunner Windows application, the reporting and analysis are mediocre in LoadRunner Cloud.

For how long have I used the solution?

I've been using LoadRunner since I started at this company one and a half years ago but the company has been using it for longer. 

What do I think about the stability of the solution?

We don't have any issues with stability. 

What do I think about the scalability of the solution?

When it comes to efficient and cost-effective scalability, it can be expensive. It is efficient, but also expensive. So the balance would then be just okay.

It's used intensively by the three performance engineers, daily. We have plans to have other teams also use LoadRunner Cloud. So we hope it will increase.

We do our own maintenance on the on-premise part and Micro Focus does the maintenance on the cloud part.

How are customer service and technical support?

We don't call customer support but we do online requests. We have put in service requests. They're helpful and the replies are quick and valuable. It helps us out.

What's my experience with pricing, setup cost, and licensing?

We make use of virtual user hours. We buy time in the LoadRunner Cloud. It costs around $80,000.

I don't think there are any additional costs to standard licensing.

Which other solutions did I evaluate?

We tried Neoload and looked at JMeter. We chose LoadRunner because that was the only performance testing tool that had something like TruClient.

What other advice do I have?

We're thinking about using LoadRunner Developer integration. We want to hand over the performance testing responsibility from our performance testing guilds to the actual feature teams, to the scrum teams, so they can do it themselves. The developers do their own performance testing in an early stage, and maybe that is a solution for that.

My advice would be to look at whether you need on-premise load generators or fully on the cloud. Invest in training. It can be complex. You need some training to get started.

I would rate LoadRunner an eight out of ten. 

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Flag as inappropriate
CM
Senior Performance Engineer at City of New York
Real User
Top 5Leaderboard
Good load-testing capability can simulate hundreds of concurrent users, but the technical support should be better

Pros and Cons

  • "The most valuable feature is that we do not have to accommodate the load-testing infrastructure in our own data center."
  • "There are three modules in the system that are different products packaged into one, and they can sometimes be difficult to figure out, so they should be better integrated with each other."

What is our primary use case?

We use LoadRunner Cloud for functional testing, where we can log in online using the portal.

Our primary use case is load testing, where we can simulate a scenario with more than 100 users accessing the system at the same time. This shows us things such as the performance of the system and how it reacts when multiple people are using it.

What is most valuable?

The most valuable feature is that we do not have to accommodate the load-testing infrastructure in our own data center. Normally for load testing, you have to have your own hardware and tools on-premises. With LoadRunner Cloud, the testing will be done remotely using their resources.

What needs improvement?

There are three modules in the system that are different products packaged into one, and they can sometimes be difficult to figure out, so they should be better integrated with each other.

The current support model is something that can be improved.

For how long have I used the solution?

We have been using this product for five years.

What do I think about the stability of the solution?

This is a stable product and as far as we're concerned, there is no other choice on the market.

What do I think about the scalability of the solution?

We are just in the process of scaling now. Our intention is to expand but it will take time to do so. We are using it for five projects right now and we need to acquire more licenses.

How are customer service and technical support?

At this time, Micro Focus is handling the support, which is kind of messy compared to going directly to HP. There is no single point of contact between sales and support.

Sometimes, if you open a ticket with technical support then we might be waiting for a week. It is not always this way, but in general, it is not what we would expect.

Which solution did I use previously and why did I switch?

We also use HP ALM for functional testing.

How was the initial setup?

The initial setup of the cloud version is easy compared to using it on-premises. In the on-premises deployment, you have to set up all of the servers starting with bare metal and it will take no less than three months to deploy. However, with LoadRunner Cloud, all you have to do is buy the resources and execute it from there.

What's my experience with pricing, setup cost, and licensing?

There is no monthly or yearly cost but rather, the fees are based on the amount of traffic that you use. It is difficult to predict the costs until after you have begun using it.

What other advice do I have?

My advice for anybody who is implementing LoadRunner Cloud is to make sure that when you buy the package, it is comprehensive. All of the modules should be there, including the support package. Otherwise, it will be hard to use.

In summary, all of the features that we need are there and it does everything that it is supposed to it. That said, the integration of modules and support are still in need of improvement.

I would rate this solution a seven out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Joe Inba
Database Leader at Skupos Inc.
Real User
Top 5
Straightforward to use and it creates a virtual infrastructure on-demand

Pros and Cons

  • "The most valuable feature is that you can create an infrastructure on-demand and do performance testing with it."
  • "Improvements to the reporting would be good."

What is our primary use case?

I have been using LoadRunner Cloud for performance testing.

How has it helped my organization?

LoadRunner Cloud allows us to do performance testing without having to create our own physical infrastructure and set up a load generator. Normally, these steps would be required.

What is most valuable?

The most valuable feature is that you can create an infrastructure on-demand and do performance testing with it. There is no need to create physical infrastructure.

Using this solution does not require the use of a load generator.

What needs improvement?

Improvements to the reporting would be good.

Technical support can be improved.

For how long have I used the solution?

I have used LoadRunner Cloud in only one project so far, for a period of about three months.

What do I think about the stability of the solution?

I have found this to be a very stable product.

What do I think about the scalability of the solution?

I only needed to simulate 40,000 users for my project but I understand that it will work for up to 2,000,000 users. That is huge and I can say that scalability is very good.

How are customer service and technical support?

This vendor, Micro Focus, is not very good at technical support.

Which solution did I use previously and why did I switch?

I have used some open-source tools and LoadRunner Cloud is more straightforward to use.

How was the initial setup?

The initial setup is normal and I have not found any complexity with it.

What other advice do I have?

I would rate this solution an eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
SP
Technical Architect at a tech services company with 51-200 employees
Real User
Good integrations, good usability and good feature sets

Pros and Cons

  • "The usability and ability to integrate with other solutions is quite good. When I use it in on Azure, then Red Hat is the most likely solution I use. When I use AWS, then I tend to use Lambda functions. In either case, it works well and you can use it either way."
  • "I don't know of any features that should be added. The solution isn't lacking anything at this point."

What is our primary use case?

We primarily use this solution to deploy our apps to the server, for public use.

What is most valuable?

The usability and ability to integrate with other solutions is quite good. When I use it in on Azure, then Red Hat is the most likely solution I use. When I use AWS, then I tend to use Lambda functions. In either case, it works well and you can use it either way.

The features on offer do everything we need them to.

What needs improvement?

I don't know of any features that should be added. The solution isn't lacking anything at this point. We're happy with what is on offer.

For how long have I used the solution?

I have had seven years of experience using this solution. It's been quite a while at this point.

What other advice do I have?

We're a customer. We don't have any business partnerships with the company.

I'd rate the solution eight out of ten overall. The solution has been quite good and integrates well with other products. It has all of the features we need and isn't really lacking anything that we've noticed.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free Micro Focus LoadRunner Cloud Report and get advice and tips from experienced pros sharing their opinions.