Amazon Redshift Reviews

We use Amazon Redshift as our data warehouse.

I found the Amazon Redshift computing services easy. I found the computing instances the most incredible in the solution.

What would make Amazon Redshift better is improvising on the pricing structure. For example, Acronis provides backups in cybersecurity, yet the pricing is a bit lesser than Amazon Redshift. I was comparing AWS, Amazon Redshift, Azure, GCP, and Acronis, and I found that Acronis has a lesser price than the other solutions in the archiving space.

I have at least two months of familiarity with Amazon Redshift.

Amazon Redshift is a stable solution.

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

I haven't contacted Amazon Redshift support because I'm not a client, but according to my subordinates, the support is excellent.

Amazon Redshift is very easy to deploy, and deployment-wise, it's impressive. It only takes two to three minutes max to deploy.

Pricing for Amazon Redshift is reasonable, though it could be somewhat higher than other solutions, such as Azure. Still, when you base your comparison on the services offered and the pricing, it's the most reasonable versus its competitors, such as RDS.

My company provides backup solutions.

I'm a business analyst with little expertise in a specific service or solution, but I've gone through all the solutions.

I have experience with Amazon Redshift.

What I'd tell others looking into implementing Amazon Redshift is that it's one of the market's best databases or data warehouses right now.

My rating for Amazon Redshift is nine out of ten.

I'm an Amazon partner.

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.

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. 

The features I find valuable in Redshift are JSON format support. You can copy JSON to the column and have it analyzed using simple functions. Second, is the parallel off/on where you can choose if you want it to unload to split files or into one file.

Since we have lots of data sources and high volumes, we needed a unified and organized DB that can handle these amounts and will be our single source of truth for the organization. Therefore, Redshift is the best solution.

It lacks a few features which can be very useful, such as stored procedures, Also, one needs to perform Vacuum in order to manage this DB. It would be nice not to worry about that and have this manageable.

Three years.

Yes. Sometimes, for some reason, Redshift is down (not due to maintenance).

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.

Great. They are available and very helpful.

Initial setup is very straightforward, very easy. No need of any side help.

If you want to think of every query you make but want to know that your nodes are fully managed, then use BigQuery Data Analytics. If you want a fixed price, an to not worry about every query, but you need to manage your nodes personally, use Redshift.

I did not. we did consider using BigQuery Data Analytics, but eventually, we decided to use Redshift.

My rating would be 8.5. This a great product, but one still needs to know how to manage clusters and nodes.

In order to make your DB scalable and reliable. it has the greatest benefit of build on PostgreSQL, so any data specialist that has SQL experience can handle Redshift.

• Performance: Very fast query performance due to columnar-storage databases that leverage the Massively Parallel Processing (MPP) capabilities of its data warehouse architecture.
• Petabyte-scale data warehouse, without any loss in performance and low cost: One of our existing customers stores more than 500 terabytes of data in an AWS Redshift database and the warehouse performance was good. We want to highlight that even if the warehouse size increases to petabytes, Redshift would still work fine and there wouldn’t be any performance issues and would cost less also.

The end users were able to have access to real-time analytics.

We would really like to see a few more connectors included that would enable connecting with other databases and services. We have faced some difficulties pulling data from Teradata and storing it in Redshift. There is no direct connector available between Teradata and Redshift.

We are working with this product for the past 24 months.

We have not faced any stability related issue so far.

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

We actually had to reach out to technical support a few times and they were really helpful and solved our problems. We would give it 4/5.

We were using an on-premise MySQL data warehouse. To reduce the cost and improve scalability, we switched to a cloud version of data warehouse databases.

Initial setup and configuration was pretty straightforward. First, we needed to create a Redshift cluster. Once the cluster was created, we created a database schema based on our need in the Redshift cluster.

AWS Redshift is one of the fastest and most cost-effective cloud-based databases. They have charged $3330 per TB/year for the ds2.8x large instances which have 244 GB RAM, 36-core CPU, 10Gbps network and 16 TB HDD.

You need to design the database structure with best sort and distribution keys, along with primary and foreign keys.

The most valuable features of this product are:

• Processing huge data in petabytes
• Massively Parallel Processing (MPP)
• Concept of data compression
• The way it stores the data in drives especially with the distribution key
• Supports BI tools like MicroStrategy (MSTR) and Tableau
• Supports all the data warehouse core features such as SCD1 and SCD2, and different schemas like the star schema

It has helped us to understand the response and interest of the customers and the user conversion rate in this competitive world. Thus, it has helped us in the decision-making process.

In most of the scenarios, the data source for Redshift will be traditional RDBMS like MySQL, PostgreSQL, SQL server, etc. After migrating to Redshift, we will find few disconnects for w.r.t data types, the stored procedures and other complex functionalities. There is a need for improvement in these aspects, mainly in the scope of data types and some complex functionalities which we can perform in RDBMS.

I have used this solution for more than a year.

I have not encountered any issues with stability. In terms of performance, Redshift is highly stable.

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

I would give the technical support a 6 out of 10 rating.

We have not used any other solution.

The setup was straightforward for those who know AWS.

The Redshift pricing policy is easy to understand.

We did not evaluate other options prior to selecting this solution.

As of now, Redshift is far better than the other products in the market.

Lastly, I would like to mention that Redshift is more about scaling and stabilizing your data. One should also focus on data modeling from time to time.

Our primary use case of this product is as a data warehouse. We are partners with Amazon. 

Amazon Redshift has a very user-friendly SQL editor and it's very easy to use the connectors. The product provides a lot of options to connect to different sources and the modeling capabilities are also good. As a fully managed data warehouse solution, the two important aspects are the connectors and how well we can use SQL for data modeling. In both cases, this is an efficient product.

Improvement could be made in the area of streaming data. The capability can definitely be improved. There are other products like Kinesis which is a separate service we use for streaming data ingestion. Whatever features are missing in Redshift, they have separate sources but if there were the feasibility to ingest real-time streaming data directly into RedShift, that would be very useful. 

I've been using this solution for the past year. 

The product is 100% stable.

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 technical support is good, they're very responsive. 

The initial setup is very simple because it's a fully managed service and not much is required from the user's end.

The licensing is paid on a monthly basis, and I think the pricing is acceptable. They also have a pay-per-go model which is on a per user basis. 

If a company is already using Amazon Cloud or they're looking for a cloud solution, Amazon is one of the oldest and most reliable cloud service providers and Redshift is a no-brainer for data warehouse needs.

I rate this product a nine out of 10. 

We use Amazon Redshift to store customer data. Basically, it's just to store our customer data so that we can use our own data.

I use Redshift Spectrum a lot, so that integration is good. Also, Amazon Redshift offers a relatively flexible structure, especially in terms of like, nodes that you can assign. Moreover, it is serverless, which is great.

Specifically, with Redshift Spectrum, some SQL commands have to run on Redshift instead of Redshift Spectrum, which slows down a few things in the tool. In the solution, user-based access is quite hard. In general, certain permissions are difficult to manage. The solution is expensive compared to Snowflake. I have used Snowflake because they're cheaper than Amazon Redshift. Some of the commands are run on Redshift itself, and some of the commands are completed by Spectrum, which is problematic. However, it is faster when computed by Spectrum.

I have been using Amazon Redshift for six to seven years. Also, I don't remember the version of the solution I am using. I think it's multiple different versions across the platform. So, I think it would be the latest version for some areas of our platform and older versions for other areas. My company has a partnership with Amazon.

Stability-wise, I rate the solution an eight out of ten. I can't remember what stability issues we had faced in the past, but I feel that it was due to overloading clusters.

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 solution's technical support is good since we have a partnership with Amazon and we have individual support. I rate the technical support a nine out of ten.

Positive

Previously, we were using Snowflake in our company. We switched since Amazon Redshift was cheaper. Now, I use Snowflake and Amazon Redshift.

I wasn't involved in the solution's initial installation. The deployment model is largely managed by our platform teams. Also, we have a team of engineers who constantly update and maintain the solution. Probably a team of engineers is specifically focused on improving our Amazon infrastructure.

I am not sure about the pricing of the tool since that's not my department. I know that Snowflake is cheaper to set up, manage, and store data. On a scale of one to ten, where one is a low price and ten is a high price, I rate the pricing a seven.

I recommended it for data storage. I don't recommend integrated solutions, like Pacemaker unless you have an advanced team to handle it. I like using it, but it's too expensive. So, I rate the overall solution a seven out of ten.