Why We Chose Redshift
blog.amplitude.com
Why We Chose Redshift
1–10 of 45 posts
Re: Why We Chose Redshift
#2Redshift is like a prison, but with excellent accommodations. It's a great platform but it pretty much the perfect example of vendor lock-in.
Re: Why We Chose Redshift
#3Redshift is like a prison, but with excellent accommodations. It's a great platform but it pretty much the perfect example of vendor lock-in.
To be fair, that kind of comes with the territory when talking about data warehousing. The data volumes are so large that migrating them is usually out of the question, and query languages vary between vendors pretty significantly.
Re: Why We Chose Redshift
#4Redshift is like a prison, but with excellent accommodations. It's a great platform but it pretty much the perfect example of vendor lock-in.
Compared to the lock-in of the AWS ecosystem in general, Redshift honestly isn't that bad. You can unload all of your data into S3 and then do whatever you want with it. I'd be surprised if most data warehousing solutions had such an easy way of exporting the data.
Re: Why We Chose Redshift
#5That extra order of magnitude you pay in pricing you gain in response time.
Re: Why We Chose Redshift
#6Curious if your funnels are just queries directly in Redshift or if there's more going on behind the scenes.
Re: Why We Chose Redshift
#7Redshift is like a prison, but with excellent accommodations. It's a great platform but it pretty much the perfect example of vendor lock-in.
Can you explain what you mean by that? I fail to see how a PostgreSQL query interface could possibly qualify as a perfect example of vendor lock-in.
Re: Why We Chose Redshift
#8That extra order of magnitude you pay in pricing you gain in response time.
Yeah, but a data warehouse isn't supposed to have great response times. Data warehouses are for large, low-value sets of historical data that you don't always know how you want to use.
If you want to use data in real-time, you should be driving it from your transactional systems. Redshift and other data warehouse solutions are for doing reporting and dashboards, not triggering real-time reactions.
Re: Why We Chose Redshift
#9The title should say 'Amazon Redshift'.
At first I thought its going to be about redshift vs f.lux:
http://jonls.dk/redshift/
Edit: Why the downvote? redshift (and flux) exist since before 2010, whereas Amazon Redshift got introduced just in 2012. I think it is reasonable to assume that someone who has never heard of Amazon Redshift would think of the open source project first (that exists in various distributions as packages), and not the Amazon service.
Re: Why We Chose Redshift
#10Curious if your funnels are just queries directly in Redshift or if there's more going on behind the scenes.
Amplitude here - Most of our dashboards are powered separately from Redshift. We offer Redshift access as a way for our customers to answer more complex questions not offered by the dashboards.