With a stable environment, it should be running very nicely. We have 203 servers for our database. So we are taking the backup of applications and databases to be on the safer side if anything happens with the CPU of Amazon.

Stability-wise, the solution is ninety-nine percent available. So, whenever we do DR setups and everything, the availability is on from primary to secondary. So there is no loss of data with or without the switch. I guess it is available with other zones and DR always. Stability-wise, I rate the solution a nine out of ten.

I would rate the stability as an eight out of ten. Improving it would be beneficial, especially during high-information processing times. The challenges arise due to the substantial volume of data, given our role as a company in the oil and gas industry.

It's quite stable and reliable, around eight out of ten. So it's a rock-solid solution.

I would rate it a nine out of ten.

I rate the stability of SAP S4HANA an eight out of ten.

With Azure, there are a lot of tools available for monitoring SAP-related information. When it comes to AWS, the infrastructure isn't specific to SAP. The monitoring and backup solutions that are available with Azure are missing with AWS.

For example, take a case for HCM enrollment. For Sonic, you need to go with the SBD devices. It should be separate. The SBD devices need to be provisioned with the three nodes with AWS. We have a fencing agent in Azure, which would be cost effective, rather than provisioning three additional VMs. It's a minimal cost, but there are additional loads which need to be done on top of it.

I would rate the stability as nine out of ten. Almost all of the public cloud providers provide the same kind of stability.

Stability has definitely improved over the years. Many customers are migrating to this solution but it requires a change in how business is done, which is too difficult for some companies. Moving involves a lot of digitization, a different GUI. 

The solution is very stable. It's reliable. There aren't bugs or glitches. It doesn't crash or freeze. Previously, there was an Oracle database, and, with HANA, they had much fewer problems with the database.

It's more of a stable landscape and the organization has to make a decision for the next generation.

The stability of the solution could improve.

I rate the stability of SAP S4HANA on AWS an eight out of ten.

The product is stable. We didn't have any issues, but there might be issues that come up because of services.

I rate the solution's stability an eight to nine out of ten.

SAP S4HANA on AWS is a pretty stable solution, and we had no issues with its stability.

S4HANA is a highly stable solution because it's on the cloud. The solution is available 24/7.

SAP S4HANA is 100% stable.

I would rate the stability an eight out of ten. 

I rate the product's stability a ten out of ten.

After the implementation phase of the product, it becomes a very stable tool.

I rate SAP S4HANA on AWS' stability an eight out of ten. 

SAP S4HANA on AWS is highly stable. I have not found any performance issues.

I rate the stability of SAP S4HANA on AWS a four out of five.

In order for us to use it so much, the solution has to be stable. 

It is indeed a stable solution, but it depends on how you architecture the component in AWS. If the component has the right architecture and is properly provisioned and placed, then it will be a stable platform.

The stability is fine. We do have a certified cloud consultant with us who is AWS-level certified and even our SAP business person is also SAP S/4HANA business certified. We do have our certified consultants who can take care of things and ensure it runs seamlessly. There are no performance issues. 

It's stable.

The solution is very stable. I rate the stability a ten out of ten.

The stability of the solution is fine. We have no issues with that.  

The solution is very stable. We've had no issues at all.

The stability is very good. There are no bugs or glitches. It doesn't crash or freeze. The solution is very reliable. 

In my experience, the product does not have any glitches or stability issues. But I do not think I am able to comment on that because I still hear feedback from people who are talking about providing solutions for issues they are having with the product. From what I hear from some people is that the product implementation still needs at least a couple of years to get real stability in the database. It is the response I am getting from the customers who have implemented it, but I have actually not actually seen it myself. It is not possible for me to say whether it is the product that has issues or if it is what the clients are doing with the product that creates the issues.  

The product has good stability

This solution has one of the most modern databases and it is very stable. I have not faced any issues with it.

It's one of the most stable virtualization softwares I have used.