Amazon Web Services vs. SAP HANA Cloud

We are using RDS for the database services. With RDS, we don't have to manage much, as most of the DBA tasks are automated. For development purposes, we are using Kubernetes pods, which makes it easy to deploy applications and scale up as needed. AWS integration with in-house applications is seamless, making it easy to keep a data-sensitive application on-premises while still utilizing AWS services.

Incentivized

SAP HANA Cloud works effectively with SMBs or small to medium-sized enterprises and requires an affordable, scalable ERP system. Companies that must implement SAP S/4 HANA as soon as possible. Companies looking to take advantage of the newest innovation from SAP are looking to cut expenses on their IT infrastructure. SAP HANA CLOUD is not suitable for 1. Large companies with intricate operational procedures. 2. Companies with stringent policies regarding data residency. 3. Businesses with a sizable SAP landscape on premises 4. Companies must closely integrate SAP HANA CLOUD with non-SAP systems.

• Starting an instance and accessing it for testing purpose, demo or production deployment its always easy.
• All the things which are available over AWS are pretty well managed and easy to use.
• You might find everything you required for an product and other development over AWS.
• Its suitable for both either an enterprise or an startup
• Various resources and documentation are available in case you struck somewhere.

Incentivized

• SAP HANA Cloud can help drive data analytics, data migration, and data management exceptionally well.
• It offers an integration service that lets you integrate data and processes with 3rd party app or any other cloud app.
• In-memory capability helps in faster data processing.

Incentivized

• The AWS Management Console can be overwhelming. so a better dashboard and organizing it would improve usability.
• The pricing models are complex. We need a more clear price calculators and cost management tools to manage our expenses better.
• Enhancements in cross service compatibility and easier third party integrations could streamline workflow.
• Simplifying model training in SageMaker and improving IAM for granular access control would make AWS more user friendly

Incentivized

• Requires higher processing power, otherwise it won't fly. How ever computing costs are lower. Incase you are migrating to cloud please do not select the highest config available in that series . Upgrading it later against a reserved instance can cost you dearly with a series change
• Lack of clarity on licensing is one major challenge
• Unless S/4 with additional features are enabled mere migration HANA DB is not a rewarding journey. Power is in S/4

Incentivized

I would gladly rely on AWS for any large-scale application deployment. For prototyping and small-scale applications, a more heavily managed environment on top of the 'bare metal' virtual infrastructure, such as Heroku or Elastic Bean Stalk, is probably a more productive approach in most cases

At this moment we are not focusing on SAP, however would love to in the future. This is primarily because of our limited ability to generate more revenue to fund for SAP partnerships and products. Our initial tryst with SAP Partneredge open ecosystem didn't go as planned and we have shelved that for now. Hope we can revive in the future

Incentivized

Amazon Web Services is a great tool when it comes to middle size organizations like us. It provides multiple tools and functionalities in low costs. The best feature we have to pay as we go. No financial burden on company for the unused instances. It also comes with greater level of security such as two level authorization such as multi factor authorization.

SAP HANA Cloud requires significant expertise on technical side to admin and manage it.It surely is lot of improvement over previous versions of SAPThe modern, role-based SAP Fiori interface has enhanced the user experience for applications like S/4HANA, though the complexity of the underlying database remains. For the average business user, the usability of SAP solutions running on the HANA database has seen a major transformation, largely thanks to the Fiori user interface.

Incentivized

Availability is very good, with the exception of occasional spectacular outages.

AWS does not provide the raw performance that you can get by building your own custom infrastructure. However, it is often the case that the benefits of specialized, high-performance hardware do not necessarily outweigh the significant extra cost and risk. Performance as perceived by the user is very different from raw throughput.

The customer support of Amazon Web Services are quick in their responses. I appreciate its entire team, which works amazingly, and provides professional support. AWS is a great tool, indeed, to provide customers a suitable way to
immediately search for their compatible software's and also to guide them in a
good direction. Moreover, this product is a good suggestion for every type of
company because of its affordability and ease of use.

Incentivized

One specific example of how the support for SAP HANA Cloud impacted us is in our efforts to troubleshoot and resolve technical issues. Whenever we encountered an issue or had a question, the support team was quick to respond and provided us with clear and actionable guidance. This helped us avoid downtime and keep our analytics operations running smoothly.

Incentivized

The API's were very well documented and was Janova's main point of entry into the services.

Professional GIS people are some of the most risk-averse there are, and it's difficult to get them to move to HANA in one step. Start with small projects building to 80% use of HANA spatial over time.

Incentivized

In my personal experience, AWS is superior to both GCP and Azure in the majority of usable applications. GCP suffers from the near total misunderstanding of how support system is even supposed to work, and while _some_ services are pretty nifty and well-polished, some are mindbogglingly designed black boxes with self-conflicting documentation. Some of it comes from having legacy systems, sure, but AWS somehow manages, even having a rather big lead start. Azure, from my limited experience, is limited to people somehow coerced into its usage by external constraints. That being said, IF you can design and implement something there, it will probably run fine.

Incentivized

It enables preview and better cloud service than other cloud platforms. Easy document transfer and faster document transfer are the key points for the selection of the HANA cloud server. The preview of data before its execution is also one of the factors in the selection of the HANA server.

Incentivized

Limitation of training deliverable by organization

Incentivized

• Provisioning resources like large database instances is really quick. We can easily scale our instances up or down as per need.
• Storing files in S3 instead of onprem NAS drives is much more economical, especially for the files stored in glacier deep archive for compliance purposes.
• Backup snapshots of EBS volumes and RDS instances may increase the cost of cloud if not cleaned up properly.

Incentivized

• perception that it is "expensive" - this is a messaging issue, not a real issue
• perception that it only runs ERP - SAP is a victim of it's own success in this regard
• perception that it isn't an industrial strength DBMS when, in fact, it is

Incentivized