Amazon Redshift Reviews

We use Amazon S3 along with RedShift for storing our data. The data comes from various sources, including our client and third-parties. We get the data as an S3 file and then load it into RedShift using the ETL tools. RedShift will then act as the data source for Tableau, which is used for forecasting and other marketing activities.

The processing of data is very fast.

It would be useful to have an option where all of the data can be queried at once and then have the result shown. As it is now, when we run a query and we are looking at the results, part of the data remains to be processed at the back end. That works very well, but in some cases, we require the whole data to be queried at once and then have the results shown. We have not faced many use cases where it would have been useful, but in one or two, we used other methods to achieve this goal.

When our clients contact customer support, they don't want to speak with a machine. Instead, they want to chat with a real person who can provide a solution. Customer service bots can provide solutions but they cannot understand our problems.

I have been working with Amazon RedShift for about two and a half years.

RedShift is a stable solution.

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.

I do not have enough direct contact with the solution to see issues that would require contacting technical support. I work with the data but not so much on the technical side. It is the developers who would see these issues and would do so. The level of support is based on our subscription plan.

The company was using other solutions such as Google Cloud and the Microsoft Cloud Service, but I have not personally used these solutions.

I am very happy with what RedShift has. So far, anything that I have required has been there and whatever use case I have faced, the functionality is available.

My advice for anybody who is implementing this solution is to look into what certifications are available and which ones are required for different roles. Depending on the job, different certifications are relevant or required. For example, as a business analyst, a coding certification would not be useful for me and it would be a waste of money. These things should all be considered before beginning with any certifications.

I would rate this solution a nine out of ten.

The primary use case for this solution is related to statistical data.

The best part about this solution is the cost.

The performance of this solution is good if you have only a few use cases and a few queries, but for larger applications, it is not so good. 

Running parallel queries results in poor performance and this needs to be improved.

This solution is stable, although we have had some issues with maintenance.

The scalability of this solution needs to be improved.

We have dealt with technical support and it is ok.

The initial setup of this solution is straightforward.

The suitability of this solution depends on the environment and the requirements. For some, Amazon Redshift is perfect. However, some people will need better queries. Based on my research, many of the products are pretty close. It is possible that the much higher priced solutions have more differences.

This is a good solution but the queries need to perform better.

I would rate this solution a seven out of ten.

We primarily use the solution for analytics.

The solution's flexibility is its most valuable feature. It's also easy to scale and has relatively painless pricing. 

The speed of the solution and its portability needs improvement.

The solution is getting more stable with each new version. It's stable now, but it can always continue to improve.

The solution can scale easily.

I've never been in touch with technical support.

The initial setup was straightforward.

We use public and hybrid cloud deployment models. We are Amazon partners.

The solution itself is very popular. Many people use it these days.

I recently went to an AWS summit in Zurich. I was very impressed by AWS and the presentation. Their solutions are very good.

I'd rate this solution eight out of ten.

We are using the private cloud model of this solution. Our primary use case is for a data warehouse for BI.

The most valuable features are that it's easy to set up and easy to connect the many tools that connect to it.

Compatibility with other products, for example, Microsoft and Google, is a bit difficult because each one of them wants to be isolated with their solutions. That's a big problem now.

It is stable.

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.

There hasn't been a need to contact technical support at this point. We haven't had any technical issues. 

The initial setup was straightforward. The deployment took a few hours. 

We integrated it ourselves. 

We have seen ROI. It's been useful.

It's around $200 US dollars. There are some data transfer costs but it's minimal, around $20.

I would rate it a ten out of ten. 

We use it to build a data warehouse and a centralized location for all of our data sources, allowing for in-depth analysis by using SQL queries.

• Allows for the storage of huge amounts of data. 
• Assists users to perform ad hoc analysis on a lot sources together.

• Windows functions, such as LEAD and LAG.
• Allows you write complex queries and perform row by row processes.

In the next release, a pivot function would be a big help. It could save a lot of time creating a query or process to handle operations.

• Storing and querying data in near real time.
• Loading millions of raw CSV records.
• Running data comparisons and queries, then shutting it all down all within a few hours, once a week.

Easy to load and reload data.

• Fast load times 
• Flexibility in column definitions
• The ability to reload data multiple times at different times.

• It would be nice if it was a bit cheaper to retain data long-term. 
• Should be made available across zones, like other Multi-AZ solutions.

Per hour pricing is helpful to keep the costs of a pilot down, but long-term retention is expensive.

Redshift COPY command, because much of my work involved helping customers migrate large amounts of data into Redshift.

It helped my customers migrate off on-premise platforms such as Teradata to Redshift, at a fraction of the cost.

There are challenges with dealing with character set mismatches. Migrating data from other data sources can be challenging when you are working with multibyte character sets.

Two years.

No.

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.

I never utilized AWS technical support.

I’ve helped customers migrate off Teradata, SQL Server , Oracle Exadata, Greenplum, and ParAccel Matrix to Redshift. Some due to cost savings, others because of the EOL of the product.

Setup of Redshift infrastructure is pretty straightforward. I’ve been told that setting up partitions can be tricky in order to ensure good performance.

I have nothing to add here as I wasn’t involved in this part of the process. However, one of my customers went with Google Big Query over Redshift because it was significantly cheaper for their project.

I only provided advice to my customers, but some looked at Azure SQL DW , Greenplum, Netezza, and Google Big Query as possible alternatives

Be careful with vendor lock-in! You cannot move your Redshift environment to a different cloud provider or to an on-premise solution.

• Easy to build out our snowflake design and load data
• Ability to dynamically increase space requirements
• Good speed
• Extremely reliable

We use Redshift as our primary BI data repository. It provides BI for all four of our product lines, which run on Redshift. It is low cost and highly reliable!

It would be nice if we could turn off an instance. However, it would retain the instance in history, thus allowing us to restart without beginning from scratch.

We have been using this a little over a year.

It is pretty easy to learn and use. If you've worked with SQL before, you won't have any problems. Also, it works very well with Talend, which is our ETL tool.

No issues of stability at this point.

No issues of scalability at this point.

I don't know that we've ever had to contact AWS for Redshift assistance. Everything is straightforward.

Not applicable.

This was our first foray into a data warehouse and customer facing BI.

We went into the project with a design in mind and Redshift provided a great working platform. Our ETL tool helped us out in building the metadata and Birst built out many of the necessary tables.

The primary implementation was done in-house, with assistance from Birst during the Birst installation.

The corporate expectation is to break-even after the first year of selling BI to our customer base. We'll know this by end of Q2, 2018. On the positive side, the addition of BI has helped close multiple sales, so we're beating the competitors with our BI tools (running on Redshift).

BI is sold to our customer base as a part of the initial sales bundle. A customer may elect to opt for a white labeled site for an up-charge.

We pretty much went with Redshift, as the company migrated everything to AWS. We might have looked at other database options, but we did not put much time into it.

Plan out your our DB design in advance and test your theories on running a small instance first. Use a good ETL tool, like Talend, so updates can be scheduled easily. Don't try to write these from scratch. Redshift has been a great DB for us to date. We haven't seen any slowdowns or outages!