News for hackers. Stuff that matters.
Re:Moving product recommendations from Hadoop to Redshift sa... by bitL on Thursday June 19, 2014 @09:28AM (#7915903)
If you optimize for latency relational databases won't cut it.
Re:Moving product recommendations from Hadoop to Redshift sa... by jpat on Thursday June 19, 2014 @09:37AM (#7915946)
I'm the author of the article. At Monetate, we've chosen our data warehouses to maximize throughput, rather than minimize latency. That's where something like Redshift really shines, it's great a large bulk ingests and running large queries relatively quickly, but awful at running lots of small queries quickly.

On our busiest day last year, we ingested over a quarter billion page views across all of our clients' websites. I'm sure someone has made MySQL scale to that volume, but for us Redshift has been working great for a relatively low price point.

Re:Moving product recommendations from Hadoop to Redshift sa... by bitL on Thursday June 19, 2014 @11:18AM (#7916538)
Thank you for sharing your experience! It's always inspiring to read well-written articles as is yours!
Re:Moving product recommendations from Hadoop to Redshift sa... by clubhi on Thursday June 19, 2014 @09:30AM (#7915910)
This might be the most inaccurate statement on the internet.
Re:Moving product recommendations from Hadoop to Redshift sa... by bitL on Thursday June 19, 2014 @10:40AM (#7916302)
OK, I should have written "if you optimize for read-access latency". Better?