Amazon Redshift Reviews

Except for the price, Amazon Redshift is a great tool and has the fastest performance across all the data warehouses we have seen. It's easy to connect with Talend, which makes it a better option to use. I like the UI better than most of the other DW. Overall it's a great DW tool.

If the number of connections is expected to be low, but the amounts of data are large or projected to grow it is a good solutions especially if there is previous exposure to PostgreSQL. Speaking of Postgres, Redshift is based on several versions old releases of PostgreSQL so the developers would not be able to take advantage of some of the newer SQL language features. The queries need some fine-tuning still, indexing is not provided, but playing with sorting keys becomes necessary. Lastly, there is no notion of the Primary Key in Redshift so the business must be prepared to explain why duplication occurred (must be vigilant for).

Amazon Redshift is well suited for fetching data from multiple different sources and servers, and it is very easy to learn how to use this tool. It is less appropriate for situations where you may need to process only limited rows, as this takes a large amount of time since you cannot create multiple tables in it.

I recommend all to use Redshift, It is easy to use and maintain. We have reduced the number of Salesforce licenses due to real-time data we have in Redshift. People are happy to use Redshift.

Amazon Redshift is good for when you need a Data Warehouse solution or a user-experience such as SQL kind queries. It is also good if you have limited budget constraints. It's not suggested when someone has DML queries such as INSERT, UPDATE, DELETE.

Redshift is appropriate when the number of concurrent users are low and pointed queries are the focus. It is not appropriate when a large number of concurrent users is to be supported,

It's very cost-effective from other databases we were using for our data warehouse. It was really easy to set up and it used our ETL tools to migrate data from different data sources. We added functionality add aggregate the data set for our Analytics team to analyze.

Amazon Redshift is the data warehouse under the umbrella of AWS services, so if your application is functioning under the AWS, Redshift is the best solution for this. For large amounts of data, the application is the best fit for real-time insight from the data and added decision capability for growing businesses. If your application is outside of AWS it might add more time in data management.

Use Redshift for data warehouses, especially if your data is already in the cloud (AWS). It's great for large datasets, and fast too, even if your dataset is column heavy. It's less so for when you have a bunch of rows. All in all, it's a good starting point for any aspiring data warehouse, but there are other promising solutions too. E.g. Snowflake.

Amazon Redshift is great for analytics, reporting, and complex queries for statistical modeling and machine learning. Its ability to run parallel queries in a simple SQL environment makes the transition from traditional DB very easy. Very good for loading/reading/writing large datasets. I would not recommend RedShift for an environment that requires single row reads/updates, which it is not optimized for.

Very well suited for aggregating/denormalizing data when you need a reporting environment. Can provide extremely fast querying for analytical purposes. Very nice to not have to have in house responsibility for sensitive data.

Not appropriate for a transactional system (though this is not what it is built for obviously). Must keep in mind the data you are syncing up to the cloud and scrub if necessary before. Something to always be mindful of of course.

[It's] very good for reports and dashboards and is easy to use and fast performance makes it a good choice. It excels in columnar architecture and aggregates. If you have many clients as we do, you need to have separate schemas for each of them. That is a good way but also there is too much clutter spread all over. That is the only drawback I see, end users can see data in the schema, there are no individual permissions allotted.

It is best for large structured data sets with data normally loaded from files, instead of through heavy SQL data manipulation. If there are SQL data manipulation, better to have mainly DDL (create/drop/alter) instead of DML (insert/update/delete) to achieve the same goals. It is also better for smaller number of concurrent connections (less than 500).

Redshift is ideal for small teams. It is fully managed. CloudWatch metrics are provided out-of-the-box, and it integrates well with other AWS products, such as DMS. The Redshift console is among the better AWS consoles. Redshift offers adequate performance. Spectrum offers a convenient way to access our data lake, but we have encountered issues with recent versions.

It is well suited for:

• Petabytes of data requiring near real-time analysis
• Massive Data Insertions
• Massive Data Reads

It isn't well suited for:

• Web apps
• Smaller transactional inserts
• Smaller reads

You wouldn't drive an 18-wheeler to the corner store to pick up a bag of chips. Your specific need will determine whether or not Redshift is suited for the job.

Redshift is a great data warehouse. It can serve the analyst team and most BI tools perfectly. Easy to learn and use. If you are using AWS then Amazon Redshift is a self-evident choice. You can use Redshift for ETL but It can be too expensive. It is not appropriate to serve as an in-production DB.

Redshift is well suited as an alternative to on-prem data warehouses. AWS Data Migration Services can be used to migrate data from various relational databases into Redshift.

Redshift is a viable platform to house a large or very large data warehouse designed for performance and scalability. It is especially well-suited in the cases where your source data is already stored inside of the AWS services infrastructure.

Well suited for faster data retrieval and powering OLTP need and perfectly suited for generating dynamic dashboards and reports.
Not suited for massive data storage and analytics. Can-not handle unstructured data.

For data warehousing and analytics, Redshift can't be beat. It's price point, minimal maintenance, and OLAP query optimization make it excellent for querying and reporting for an organization with a small budget. As long as you can live without some standard database tools like constraints and stored procedures, it is an excellent database.

It's the best option when we need to have a high volume of structured data analytics datawarehouse design & development. It perfectly reports fast with tableau reporting tool, even data around 300 million records. It's best suited where the organization is planning to build a custom datawarehouse rather than using any pre-packaged BI Apps data model.

If you are using Google Analytics 360, then Googel BigQuery would be more appropriate. However for companies with big transactional data that want to do complex SQL querying--it could be a good choice.

It's well suited to be used in an analytics environment where the consumers are 1-50 analysts who need to write complex queries against the data, where total data size is in the 1TB-1000TB range, and where there's no need for data latencies less than one hour. It won't work well in the PB scale, where there are too many consumers and data producers, and for real time applications.

If you want an easy way to get started with a column store, spin one up on AWS and see if it fits your use case. AWS is a reasonably cheap way to adopt new technologies. Then after a while, you'll be in a better position to decide whether to commit more to AWS or choose from comparable technologies available.