The documentation isn't clear enough. There are a few native services that are available for increasing the IOPS. We can either go for the database storage striping to improve the IOPS for the HWCCT requirement, or we can go for the data volume partitioning, which is available with HANA for increasing the IOPS.
It would help during maintenance to add new storage due to the data growth. It would be easy to go for the data volume partitioning feature with HANA. It's available even with other databases, but there's no comparison with the different features.
There are a few features that are in-built and available with SAP. When it comes to the on-premises solution, we used to go with those options. When it comes to the cloud, most people compare it to their past experience with the on-premises environment rather than the new cloud solutions. They might have an in-house benchmarking comparison or test results for those things, but it would be good if they published that. It would be very helpful for us when we need to take a particular call, or when we need to go for data volume partitioning or data striping.
In Azure, files can be downloaded and easily repurposed based on our solutions, which is lacking in AWS and in GCP.
I have used this solution for the past seven years.
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.
The scalability is good.
SAP has an auto-scaling feature, but Azure doesn't.
There weren't a lot of challenges with the setup.
I would rate the setup as five out of five.
It's expensive. It would be good if AWS and Azure could reduce the computing cost for people who move to the public cloud.
I would rate the pricing as four out of five.
There's not a lot of difference in the pricing of AWS and Azure. AWS is about $1 or $2 higher than Azure. Azure is cheaper when it comes to the computing part. From the partner side, I feel we are getting more benefit when it comes to Azure Cloud.
I would rate this solution as nine out of ten.
When it comes to Azure, if you're already using existing solutions, it's easy to leverage that into a public cloud.
There are challenges with implementing AWS in India, but not Azure.