25 engineers on Hacker News describe using Amazon Redshift first-hand: 3 endorse it, 5 regret it, 3 are mixed.
“We switched to Snowflake, saved money, got better performance, and had a simpler setup.”
regret · production · nijave · 2026-05-10 · source ↗ · wrong label?“we started having performance issues. We migrated from Redshift to Snowflake”
regret · production · matthewhefferon · 2025-05-20 · source ↗ · wrong label?“we migrated from Redshfit, which had 7-30 second performance.”
regret · production · koromak · 2024-06-11 · source ↗ · wrong label?“Redshift complains loudly if you try to insert a DECIMAL(38,17) into a DECIMAL(38,18) column”
regret · production · ctc24 · 2022-12-12 · source ↗ · wrong label?“We run almost all analysis off of Redshift, but have a natural backup of data stored elsewhere.”
endorse · production · sturgill · 2017-12-23 · source ↗ · wrong label?“There's no reserved instances market for Redshift... we have to let all of our small node reservations expire before”
regret · production · endymi0n · 2017-09-27 · source ↗ · wrong label?“We run into problems with Redshift all the time and they are quite responsive (well they do violate their SLA often and we are too nice to deal with that right now).”
mixed · production · yeukhon · 2015-10-02 · source ↗ · wrong label?“We switched to Redshift for our data warehouse because it was MUCH cheaper, declarative, allowed us to retain the relational model”
endorse · production · crdb · 2014-06-19 · source ↗ · wrong label?“we're still an order of magnitude away from Infobright's query performance... we've not run it on more than a 6 XL cluster yet.”
mixed · personal · vosper · 2013-11-12 · source ↗ · wrong label?“We use Redshift in production to power a customer-facing app, but don't have web apps hit it directly”
mixed · production · onemoreaccount · 2013-11-12 · source ↗ · wrong label?“I did some testing using pretty small dataset... it does look promising and it should only get better.”
endorse · personal · sloth0000 · 2013-11-12 · source ↗ · wrong label?“our biggest care and feeding task was adding new event types to our kafka-to-redshift ETL thing”
neutral · production · EamonnMR · 2023-08-07 · source ↗ · wrong label?“In the end, we moved to Amazon Redshift, and he was progressively moved into a smaller and smaller role”
neutral · production · Simon_O_Rourke · 2022-05-09 · source ↗ · wrong label?“We've phased out Kafka for the parts that feed Redshift”
neutral · production · lflux · 2020-03-27 · source ↗ · wrong label?“Stitch -> Redshift (with DBT for data modeling) -> Looker”
neutral · production · mjirv · 2019-11-12 · source ↗ · wrong label?“we use both Postgres and Redshift here, too”
neutral · production · yellowapple · 2019-03-21 · source ↗ · wrong label?“Redshift for stats/reports.”
neutral · production · InGodsName · 2018-12-26 · source ↗ · wrong label?“we built end points in Go which collect data and post it to Bigquery or Redshift.”
neutral · production · InGodsName · 2018-12-15 · source ↗ · wrong label?“We use AWS Redshift. You have the option to import data into Power BI”
neutral · production · go_prodev · 2018-12-10 · source ↗ · wrong label?“For large quantity work we've moved to AWS Redshift.”
neutral · production · eyepulp · 2016-03-14 · source ↗ · wrong label?“have been using more and more ACTUAL AWS services (SQS, DynamoDB, Redshift)”
neutral · production · atonse · 2014-12-19 · source ↗ · wrong label?“although a fair amount of ad-hoc work is done in RedShift.”
neutral · production · tcoupland · 2014-10-27 · source ↗ · wrong label?“In production I've used Oracle DB, MySQL, PostgreSQL, MongoDB, DynamoDB, Cassandra, Google Cloud Datastore, Redis, RedShift and Elasticsearch.”
neutral · production · nielskrijger · 2014-10-19 · source ↗ · wrong label?“We then load those events from S3 into Redshift and Postgres.”
neutral · production · alexatkeplar · 2013-11-10 · source ↗ · wrong label?