We mainly use the solution for marketing analytics.
Senior Data Scientist at a tech services company with 51-200 employees
The solution works fast and we use it for marketing analytics
Pros and Cons
- "The solution is scalable. It handles different loads very well."
- "They should provide a better way to work with interim data in a structured way than to store it in parquet files locally."
What is our primary use case?
What is most valuable?
The solution works fast. I use Redshift to clear a lot of web page data. I use it mainly as an extraction tool to obtain the information I need for a project and store it in parquet files on a disk. Later, I work on the data using Python. I write back all my final results to Redshift and store the temporary files on a local machine.
What needs improvement?
They should provide a structured way to work with interim data than to store it in parquet files locally. Also, Redshift is unwieldy. There should be better integration between Python and Redshift. It could be more accessible without using so many sequels.
They should make writing and reading the data frames into and from Redshift easier. The performance could be better. I have used Redshift for extensive queries. For the large tables, it's easier to unload to Redshift, but subquery tables that run complex grids are slower for configuration. I have to use the unloaded command to unload the whole table. Further, I have to read the table into a server with extensive memory in Python and process the data ahead. It's not optimal.
For how long have I used the solution?
We have been using the solution for two years.
Buyer's Guide
Amazon Redshift
November 2024
Learn what your peers think about Amazon Redshift. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
814,763 professionals have used our research since 2012.
What do I think about the stability of the solution?
I rate the solution’s stability as a nine.
What do I think about the scalability of the solution?
The solution is scalable. It handles different loads very well. We have 80-100 users using the solution in our company.
How was the initial setup?
The setup was quite complicated. For instance, if you use AWS Glue to automate loads into Redshift, setting up the security for the requirements between the two is complex. I've struggled a lot to set up the cluster on VPC and to get all the endpoints set up correctly with the right access and services. Especially from Glue's endpoints, I had to repeat the same process every time. It consumes a lot of time. In comparison, the CloudOps executives do the setup very quickly.
What's my experience with pricing, setup cost, and licensing?
I have heard complaints about the solution’s pricing, and thus I rate it as a five.
What other advice do I have?
I rate the solution as an eight out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Senior Solutions Architect at a retailer with 10,001+ employees
Merges and integrates well with all databases; lacks transparency
Pros and Cons
- "This service can merge and integrate well with all databases."
- "Planting is the primary key enforcement that should be improved."
What is our primary use case?
We are premium partners with Amazon.
What is most valuable?
This service can merge and integrate well with all databases.
What needs improvement?
Planting is the primary key enforcement that should be improved but there is probably a reason that they don't follow the reference architecture. It means they are creating clones of the data shading. Cost control measures could be improved along with added transparency.
For how long have I used the solution?
I've been using this solution for nine months.
How are customer service and technical support?
AWS technical support is very good.
How was the initial setup?
We needed some help from experienced professionals for our initial setup.
What's my experience with pricing, setup cost, and licensing?
Licensing costs are reasonable.
What other advice do I have?
I would recommend this solution depending on the scale. You need to decide whether you want to be lined up with a single cloud provider or go over the service and have it deployed on multi cloud. There are many factors to take into consideration.
I rate this solution seven out of 10.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
Amazon Redshift
November 2024
Learn what your peers think about Amazon Redshift. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
814,763 professionals have used our research since 2012.
Senior Consultant at Dynamic Elements AS
Its encryption features help us secure our data on the cloud
Pros and Cons
- "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."
- "Redshift's GUI could be more user-friendly. It's easier to perform queries and all that stuff in Azure Synapse Analytics."
What is our primary use case?
We use Microsoft Azure, but one of our clients is on AWS, so we did a POC for Amazon Redshift. Now, it's up to them to make the call on whether to continue with the solution based on pricing and their needs.
What is most valuable?
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.
What needs improvement?
Redshift's GUI could be more user-friendly. It's easier to perform queries and all that stuff in Azure Synapse Analytics.
For how long have I used the solution?
I have been working on Amazon Redshift for six months, but I haven't used the solution extensively because we only did a POC for one client.
What do I think about the stability of the solution?
I think Redshift is stable. There shouldn't be any issues.
What do I think about the scalability of the solution?
Redshift is serverless, so you can scale it as needed. If the amount of data increases, the nodes will automatically be connected.
How are customer service and support?
We haven't contacted Amazon support yet because we didn't encounter any issues that required support from Amazon, but I imagine it's comparable to the service we get from Microsoft.
Which solution did I use previously and why did I switch?
I've worked with a couple of cloud-based database solutions like Amazon Redshift and Azure Synapses,
How was the initial setup?
Setting up Redshift is a little complex and requires some prior knowledge, whereas Azure's GUI is more intuitive and it's easier to navigate the steps.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Engineering Manager/Solution architect at a computer software company with 201-500 employees
Fast and easy to manage; offers good API, analytics, and integration
Pros and Cons
- "Setup is easy. It's a fast solution with machine learning features, good integration, and a good API."
- "This solution lacks integration with non-AWS sources."
What is our primary use case?
We use this solution for our enterprise data warehouse.
We use it for scaling our warehouse.
We also use it for analytics.
What is most valuable?
A feature I find most valuable in Amazon Redshift is that it's fast.
I also like that you can query the data lake using the Redshift spectrum.
You can build analytics on this solution, similar to QuickSight or Tableau, based on the Redshift Data API.
Amazon Redshift also has good integration and a good API. It's not hard to manage. It even has machine learning features.
What needs improvement?
This solution could be cheaper, but Amazon could constantly add new instances and decrease the size from previous ones, so it could be an AWS work model.
It would also be better if it can be integrated with non-AWS sources, e.g. additional open source connectors.
For how long have I used the solution?
We've been using Amazon Redshift for a long time. We've been using it for years.
What do I think about the stability of the solution?
This solution is stable.
What do I think about the scalability of the solution?
I find this solution scalable to a great extent.
How are customer service and support?
Amazon's technical support works fine.
How was the initial setup?
Setup was easy. This is a managed service, so you don't need to install anything. You just choose the size of the cluster and within 10 to 20 minutes, it's built.
What's my experience with pricing, setup cost, and licensing?
This solution implements the pay-as-you-use model, so no license. It's just for underlying infrastructure.
Which other solutions did I evaluate?
I evaluated Cloudera and Azure.
What other advice do I have?
We usually rely on some distribution, not like classic Hadoop. We do not use open source Hadoop because our customers prefer some distribution to get support. Some paid features from Cloudera and Amazon provide their own support.
We provide expertise for different services of AWS, e.g. most of them because we are a premium partner and we have program competencies. We develop data, big data, machine learning, and migration, so we cover a large field.
We have some clients with Azure, but most of our clients are with AWS.
The deployment of Amazon Redshift is through AWS. It's a home-based, proprietary solution. It's fully managed by AWS.
Amazon Redshift has implemented most of the features that we currently need, so I can't name additional features that I expect from them in the next release.
The number of people needed for the deployment and maintenance of this solution in our organization is just one: only to set up. It's just one DevOps.
I would recommend Amazon Redshift as a solution for others who are thinking about using it.
I'm rating Amazon Redshift an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Data Analyst at a tech vendor with 51-200 employees
Has improved the performance of queries
Pros and Cons
- "The initial setup is easy."
- "The solution has four maintenance windows so, when it comes to stability, I think it would be better to decrease their number."
What is our primary use case?
We are using the latest version of Amazon Redshift, although I cannot state which one. It is actually updated automatically, which prevents us from tracking it.
We use Amazon Redshift as our data warehouse solution. We use it for collecting and analyzing our data. We store our data for analytics in the solution.
How has it helped my organization?
The solution has improved the performance of our queries.
What is most valuable?
We like that the solution is a scalable, column-store database. We are completely talking about an analytic database.
What needs improvement?
I cannot state which features of the solution are in need of improvement, since those which we make use of have not changed.
The solution has four maintenance windows so, when it comes to stability, I think it would be better to decrease their number.
I rate the solution as an eight out of ten because it is not 100 percent, as there is much service-related maintenance required. It would be nice to see support for the usual LTP features, such as those involving traditional processing.
What do I think about the stability of the solution?
The solution has four maintenance windows so, when it comes to stability, I think it would be better to decrease their number.
What do I think about the scalability of the solution?
The solution is scalable.
We use the solution extensively, as part of our daily work.
The decision to increase our usage would depend on our business needs.
How are customer service and support?
I cannot comment on technical support, as I have never had contact with them.
Which solution did I use previously and why did I switch?
Prior to going with Amazon Redshift, I used Azure Data Warehouse and Google BigQuery.
The decision to go with Amazon Redshift was reached by the CTO, so that, in respect of the data warehouse, the entire environment is set up in Amazon.
I feel Amazon to be better than the other solutions we worked with.
How was the initial setup?
The initial setup is easy. Just one or two clicks are needed to set up the solution.
What about the implementation team?
We did not make use of a consultant or integrator.
Not much staff is required to maintain the solution.
What's my experience with pricing, setup cost, and licensing?
I am not aware of the licensing terms.
What other advice do I have?
I am just the user and we make use of the solution.
The solution is deployed solely on the cloud.
I believe there are around 20 people making use of the solution in our environment.
While the solution is not appropriate for every case in which usage must be evaluated, it can be used for sure.
I rate Amazon Redshift as an eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
CEO at Screenit Labs Pvt Ltd
Good support and provides on-the-fly analytics capabilities, but it needs to be more user-friendly
Pros and Cons
- "The feature that we find most useful is the ability to do analytics on the fly."
- "In our experiments, the handling of unstructured data was not very smooth."
What is our primary use case?
We are a solution provider and Amazon Redshift is one of the products that we implement for our clients. We are working with a few customers that have it implemented right now.
What is most valuable?
The feature that we find most useful is the ability to do analytics on the fly. It's the most important because it gives us the ability to provide solutions to multiple customers.
What needs improvement?
We have had some challenges with respect to considering some of the high-end availability architecture for production. We don't find many issues now, but initially, we had some challenges.
This is an older product, so when it comes to usability, it requires a technical person to work with it. It requires a specialist and a good business case to work on it. It has to be a little more user-friendly than what it is today.
In our experiments, the handling of unstructured data was not very smooth.
For how long have I used the solution?
We have been using Redshift for the last year and a half.
What do I think about the stability of the solution?
It is fairly stable and works reasonably well.
What do I think about the scalability of the solution?
We tested the scalability to 10 or 15 terabytes and we didn't have an issue with it. I'm not sure what the limit is.
How are customer service and technical support?
The technical support is very good and they have helped us to move forward with this product. We also had a lot of good support from the community, as well.
How was the initial setup?
It is not complex for a specialist because it is fairly well documented and systematic.
The specialists required by this product are what you will find in most enterprises. However, in a smaller organization, you might have to engage multiple parties with separate expertise to set it up correctly. For example, you will require somebody with experience in database migration to the cloud.
What's my experience with pricing, setup cost, and licensing?
At the moment, pricing is a little bit on the higher side, although it depends on the size of the company. If it's a fairly large enterprise that has a defined budget then they may not have too much of an issue with the pricing.
Which other solutions did I evaluate?
We have also tried Cosmos DB and Azure for our customers, but they were not chosen after the PoC. Azure and AWS have different database offerings and we experimented with both, but the customer ended up in production and we stayed with that.
What other advice do I have?
My advice for anybody who is implementing Redshift is to ensure that the requirements include having technical people on board to continuously work on getting the results you want. Because it's not that user-friendly, there is a need for a technical resource in the company.
Also, I would suggest watching out for scalability beyond what we have tested. If there is a need for scaling then it should be tested, although it depends on the use case.
If Redshift had a proper interface then I would score it higher.
I would rate this solution a seven out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
Manager Data Services at a logistics company with 201-500 employees
Gives us the ability to increase space requirements
Pros and Cons
- "Easy to build out our snowflake design and load data."
- "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."
What is most valuable?
- Easy to build out our snowflake design and load data
- Ability to dynamically increase space requirements
- Good speed
- Extremely reliable
How has it helped my organization?
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!
What needs improvement?
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.
For how long have I used the solution?
We have been using this a little over a year.
What was my experience with deployment of the solution?
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.
What do I think about the stability of the solution?
No issues of stability at this point.
What do I think about the scalability of the solution?
No issues of scalability at this point.
How are customer service and technical support?
Customer Service:
I don't know that we've ever had to contact AWS for Redshift assistance. Everything is straightforward.
Technical Support:Not applicable.
Which solution did I use previously and why did I switch?
This was our first foray into a data warehouse and customer facing BI.
How was the initial setup?
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.
What about the implementation team?
The primary implementation was done in-house, with assistance from Birst during the Birst installation.
What was our ROI?
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).
What's my experience with pricing, setup cost, and licensing?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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!
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Data Scientist at a tech vendor with 51-200 employees
Though it offers a relatively flexible structure to its users, it's hard to manage its user-based access
Pros and Cons
- "Amazon Redshift offers a relatively flexible structure...I rate the technical support a nine out of ten."
- "In the solution, user-based access is quite hard. In general, certain permissions are difficult to manage."
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
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.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Previously, we were using Snowflake in our company. We switched since Amazon Redshift was cheaper. Now, I use Snowflake and Amazon Redshift.
How was the initial setup?
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.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
Download our free Amazon Redshift Report and get advice and tips from experienced pros
sharing their opinions.
Updated: November 2024
Product Categories
Cloud Data WarehousePopular Comparisons
Azure Data Factory
Snowflake
Teradata
Microsoft Azure Synapse Analytics
Oracle Exadata
Vertica
VMware Tanzu Data Solutions
AWS Lake Formation
Amazon EMR
Apache Hadoop
Oracle Autonomous Data Warehouse
SAP BW4HANA
IBM Netezza Performance Server
Oracle Database Appliance
Buyer's Guide
Download our free Amazon Redshift Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Which ETL or Data Integration tool goes the best with Amazon Redshift?
- What is the major difference between AWS Redshift and Snowflake?
- What is the biggest difference between Amazon Redshift and Vertica
- How does Amazon Redshift compare with Microsoft Azure Synapse Analytics?
- What are the challenges faced during migrating from Netezza to AWS Redshift?
- Which ETL or Data Integration tool goes the best with Amazon Redshift?
- What are the main differences between Data Lake and Data Warehouse?
- What are the benefits of having separate layers or a dedicated schema for each layer in ETL?
- What are the key reasons for choosing Snowflake as a data lake over other data lake solutions?
- Are there any general guidelines to allocate table space quota to different layers in ETL?