Scalability is always available in the solution. So if we go with scaling up its storage part and decide to have an eighth or twenty-four TB storage is possible with high quality and production. Nowadays, forty-eight TB is supported by AWS, and the medium will be twenty-four TB for SAP S4HANA. As a requirement, we can deploy, you know, our requirement with six GB or maybe twenty GB requirement. So we have to do calculations, and the customer can tell us how much TB they need. I recommend it for those who want to analyze data and identify if they need 24 TB storage with all the backups, servers, and everything.

The size of our clients depends on the data. The size of the data depends on ECC, GRC, and BW parts.

I would rate the scalability of the solution as an eight out of ten. My company uses SAP S/4HANA on AWS 24/7 and we have about 100 users.

I would rate the scalability an eight out of ten. We currently have around 400 to 500 users.

I would rate it a eight out of ten.

We have approximately 20,000 people using the solution in my organization. We do not have plans to increase our usage.

As the company continues to release new updates, simplification, and expansion, the scalability has increased.

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

The scalability is good. 

SAP has an auto-scaling feature, but Azure doesn't.

The solution is scalable. 

The product is scalable. It works well with large organizations. It was a very big implementation. In the Netherlands, we had around 160,000 workers for the central government, and all the HR processes and the salary payments were performed with SAP. 

We do not have plans to increase this number of users, as the Dutch government is growing, however, not that much.

We have approximately 100 people using the solution in my organization.

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

I rate the solution’s scalability an eight-point five out of ten.

SAP S4HANA on AWS is a scalable solution. Over 200 users are using the solution in our organization.

S4HANA on AWS is scalable. We currently have three clients on it: OiServe, HSDM, and NDEP. The others are using on-premise solutions. So I will count those ones.

SAP S4HANA is scalable.

I would rate the scalability an eight out of ten. Around 300 to 700 end users have been using this solution. 

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

Scalability-wise, I rate the solution a four out of ten.

The capability of the product to integrate with other applications is one of the biggest problems I face when dealing with the implementation process.

Most of my company's clients who use the solution are medium-sized businesses.

It is scalable.

The scalability of SAP S4HANA on AWS is very good.

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

The solution is scalable. 

The solution can scale. We just have to identify how many users are there since we have to identify the instance of the database. That is very important. The common instance of the database needs to be created so we need to identify properly and number of CPUs, number of database instances, et cetera. All those things should be identified and once those are properly identified, then making and implementing the system and designing the system and running the system is not an issue. 

We have three clients that deal with this product.

It's scalable. It's about 70% scalable.

I rate the product’s scalability a nine or ten out of ten. Our customers are medium and large enterprises.

For scalability, the skill set required is very specific. You need someone who has a functional and business knowledge along with technical knowledge. A candidate or the consultant who has experience in the difference between the data technological concerns and the business trends can easily go through the entire deployment very easily. Having industry experience is very much required for deployment and scaling.  

The solution is scalable. With the new data connectors that they have and the new FCI NCPI integration facilities, it can be scaled up with any other third party component or even Zippy products.

The solution scales well. You can integrate almost any application with SAP and you can pull data from SAP or input data in SAP.

We have more than 20 SAP clients, however, only five are on the cloud.

I don't think it would be right for me to comment on that package regarding the scalability. I don't think it should be a problem, but as far as having the experience with the product to be sure, I am not at that point. It is too new and I am just helping clients who are implementing it right now.  

The maintenance of this product requires a different number of staff members depending on the deployment model. I think a customer will need to make their own decisions about this. Accountability on an outside service will be very different than in house. In house, you will be dealing with a team of three to five people. These will be some kind of functional experts who will be performing in different capacities. The size of the team will depend on what the company is planning on using and what they need to deploy and maintain. So for some clients, they may need a bare minimum of 4 to 5 people and then, in addition, they may need other support services.  

The scalability is fine. 

We have approximately 1,000 people using the solution in my organization. The solution is scalable.

This solution is scalable if you are talking about the functional or technical side.

I have a customer with nine hundred branches and has not faced any issues.

We have five to fifteen users consisting of our application team, infrastructure team, and some of our clients. 

For the maintenance of this solution you would need first, second, and third-level, so around five people in total. 

Scalability lacks on clustering capabilities. 

Our clients are mostly enterprise size.