Amazon Redshift pros and cons

It's scalable because it's on the cloud.

The feature that we find most useful is the ability to do analytics on the fly.

Changing from local servers to the cloud is very easy. It's so nice not to have to worry about physical servers.

Setup is easy. It's a fast solution with machine learning features, good integration, and a good API.

The initial setup is easy.

I find the most valuable features to be the MPP style of processing, which mostly all of the data warehouses provide. The ability to integrate all other AWS services, such as NSS and S3, with little effort is very helpful. The service is well maintained, there are update patches frequently.

Amazon Redshift is very fast. It has really good response times. It's very user-friendly.

Has a very user-friendly SQL editor and it's very easy to use the connectors.

Redshift's versioning and data security are the two most critical features. When migrating into the cloud, it's vital to secure the data. The encryption and security are there.

For the on-premises version of Amazon Redshift, we need to start from scratch. However, with the cloud version whenever you want to deploy, you can scale up, and down, and it has a data warehousing capability. Redshift has many features.

I would like to improve the pricing and the simplicity of using this solution.

In our experiments, the handling of unstructured data was not very smooth.

The refreshment rate of data reaching Redshift from other sources should be faster.

This solution lacks integration with non-AWS sources.

The solution has four maintenance windows so, when it comes to stability, I think it would be better to decrease their number.

We recently moved from the DC2 cluster to the RA3 cluster, which is a different node type and we are finding some issues with the RA3 cluster regarding connection and processing. There is room for improvement in this area. We are in talks with AWS regarding the connection issues.

There is some missing functionality and sometimes it's so difficult to work in. We need to convert these functionalities using VACUUM inside Amazon Redshift and then it causes some complexity.

Improvement could be made in the area of streaming data.

Redshift's GUI could be more user-friendly. It's easier to perform queries and all that stuff in Azure Synapse Analytics.

We are using third-party tools to integrate Amazon Redshift, they should create their own interface on their own for it to be easily connected on the AWS itself.