My company has more than 100 users. 

I would rate the scalability as ten out of ten.

I would rate scalability a seven out of ten. There is a need for improvement in terms of scalability. 

Amazon Redshift is a scalability solution.

If we can immediately set up new servers, it's easy to do, but an automatic solution or a threshold would be ideal. This feature may be already available, but I'm not sure. We have three users using this solution. I rate the solution’s scalability a seven out of ten.

The tool’s scalability is pretty good. I rate the scalability an eight out of ten.

There is no issue with the solution's scalability.

We have no problems with scalability.

The solution's scalability has been fine regarding how much data we can load into it. Once the solution is set up, we pay for what we use. Three people are using the solution in our organization.

We have to consider the scalability of this solution carefully. In production, we have a proper size. We allocate 40% for data storage and 60% for temporary segments. We cannot increase data storage usage beyond 50%. It cannot exceed 80% of the total utilization, including network speed and query performance. We monitor all of these carefully.

So if the CPU utilization goes beyond 80%, I recommend upgrading to multiple nodes. It ensures that there won't be any issues. Around 30 people are using AWS and Azure modules along with me.

Around 20 people in our organization use the product. The tool’s scalability is good.

This solution is scalable. We scale up and scale down manually when we are required to, we do not have an automatic setup.

We have three or four people using this solution.

It's scalable as it's on hosted and Managed on AWS cloud.

The scalability of Amazon Redshift is good.

We have approximately 20 people using this solution in my organization.

It's very scalable.

The solution is scalable. It handles different loads very well. We have 80-100 users using the solution in our company.

If you require a highly scalable solution, I would not recommend Amazon Redshift. We currently have 12 clients using Amazon Redshift, and the scalability of the solution is terrible. In terms of scalability, I would rate this solution a three or four out of ten.

We have 16 Redshift users in our company, and I'd rate the scalability at ten out of ten. 

Redshift is serverless, so you can scale it as needed. If the amount of data increases, the nodes will automatically be connected.

There are three people in my organization using this soltuon.

Amazon Redshift is a scalable solution that also suits enterprise companies.

The tool is highly scalable. I'm a freelancer, so I use the solution in different contexts, but the total number of end users is usually between 100 and 200.

We did not encounter any scalability issues in the last 24 months that we have been working with Redshift.

I find this solution scalable to a great extent.

The solution is scalable. This is backend technology and end users are not aware they are using it. We probably have four or five users in the company. 

The solution is scalable.

We use the solution extensively, as part of our daily work.

The decision to increase our usage would depend on our business needs.

We tested the scalability to 10 or 15 terabytes and we didn't have an issue with it. I'm not sure what the limit is.

No issues of scalability at this point.

Once we moved to a serverless version, it became more scalable. The concurrency of queries on the same cluster has a big scalability issue. Scalability-wise, I rate the solution a seven out of ten.

Around 300 people in my company use the solution.

The scalability is very good, and it is one of the best features of this solution.

We have approximately 10 people who use it, four of which are engineers. At this point, we do not have plans to increase the number of users.

Scalability can be a problem if you don't write your database queries correctly. For example, if you write a cartesian product in Redshift then you may end up consuming all of the resources. However, it does have features like workload management to prevent this from happening.

Our clients are mid-sized to very large companies.

Scalability is okay. It's easily scalable. We don't have any plans to increase usage at the moment. We currently have two users directly using this solution. Indirectly we have around 50 users.

We require two staff members for maintenance and others are just consuming data from it.

The scalability is very good. You can start at a very low scale and just keep expanding as required. It is the type of product that fits organizations of all sizes.

Ofcourse. When the amount of data that we handle in the cluster grew, we need to increase the cluster or node size. Apparently, the size of node or cluster increases the hold time for synchronizing the data (meta data) with the node manager. The initial time increases when we start the cluster.

No scalability issues whatsoever.

I have not experienced any scalability issues.

I have not encountered any issues with scalability. We can easily scale the nodes in AWS only with a few clicks.

The scalability of Amazon Redshift is good. The solution is best suited for larger-scale businesses because the price is affordable for them and they need the complexity.

Since Redshift is on AWS cloud, scalability is not an issue. With a few clicks, cluster size can be increased or reduced. This is useful especially when you expect a large amount of data processing temporarily. For example, on Black Friday retail organizations expect large amounts of data flow/processing. Redshift can be scaled up for few days to accommodate the surge of data and then scaled back to normal cluster size to save OPEX.

I personally haven’t hit scalability issues but at dinner a year ago with a few of my existing customers (all Fortune 500 companies), I was told there are scalability issues once you get to 32-nodes.

One of my previous customers told me they were migrating off Redshift because they hit the ceiling and had scalability issues. They told me the responsiveness they were getting was inferior to alternative solutions once your Redshift gets to a specific size.

No, cause we know how to use Redshift. We have a cluster of both HDD and SSD for which we keep the maximum data in each, so it would be scalable.

We did not encounter any issues with scalability.

Redshift can scale up to a petabyte with a few simple clicks.

Given that RedShift is a cloud-based solution, scalability is very good. I have not faced any issues regarding that. We have about 20 users, who are all developers.

Beyond the development stage and in terms of the users who make use of the data for Tableau, there are many people all around the world. I do not know the number, but it could be 1,000 or it could be 10,000. When it leaves us and goes into production, it is the client who takes care of it. One of the clients I am working with now has more than 10,000 personnel.

The time it takes to scale the cluster up or down is not trivial and it can take a while. In case you need to do this fast, you will need to think about other solutions.

Redshift has had some scaling issues, but Redshift's performance overall is excellent. 

The scalability of this solution needs to be improved.

The solution can scale easily.