4.3 out of 5 (21 Ratings)
Mar 21, 2017
What worked well - using the Platform as a service - no need for indexing, partitioning etc - amazing compression - MAtillion (an AWS Marektplace ELT tool) proved very good at transferring SQL Server to Redshift What didn;t work well - poor support (AWS are too busy/successful) - performance not as stellar as had been led to expect. A significant level of specialist tuning is still required - even when top of range hardware deployed for demo-
Mar 14, 2017
Mar 8, 2017
We experienced very fast query performance. The ease of implementation was great.
Mar 2, 2017
Great documentation and well articulated guides on implementation. RedShift fits well into existing AWS VPC investments and security practices.
Feb 28, 2017
It was difficult to speak directly with an AWS technical person. It was much easier through a 3rd party that had a relationship with AWS.
Feb 21, 2017
Redshift is overall a good product. We are willing to live with its shortcomings for the overall lower cost. It has served us well so far.
Jan 26, 2017
Great - positive experienece
Jan 25, 2017
Pro: well documented, built on standards (PostSQL), so easy to learn Cons: requires deep query expertise to ensure queries complete in a reasonable amount of time
Jan 19, 2017
AWS has made our companies growth extremely easy. Redshift has proven to be a valuable resource for us.
Jan 18, 2017
Easy to turn on, deploy, and experiment with. With AWS Redshift, an important piece of the technology is that it works best in a cluster. Single nodes aren't performant at all due to how the horizontal scaling architecture works, but are fine for development. Additionally, scaling writes has proved challeging. At launch, we appended data to 100 tables every 15 minutes. But, once read load was applied, it brought the cluster to a hault. Reducing our load intervals and increasing our cluster size solved all issues.