Live data from Hacker News

Why We Chose Redshift

blog.amplitude.com

31–40 of 45 posts

Re: Why We Chose Redshift

#31

How do you guys handle the constant shifting of analytic schema that happens when handling a fast iterating application?

We update the table schema as we run into new fields, up to a limit. We also store the unstructured part of the data in a column that can be queried via json_extract_path_text.

Re: Why We Chose Redshift

#32
post #26

Earlier quoted context omitted.

The UI colorizer is what I thought of immediately, too. If we took a poll I suspect the majority would be thinking of the Amazon service That's just personal projection, and is as irrelevant as an argument beginning with, "I think most people would agree that..." Personally, regardless of Amazon vs UI hack, I'm really tired of ambiguous naming in tech projects.

I'm much more tired of comments on ambiguous naming. There are at least two other people in my city who have my name, and many more who share either my first or last name. Somehow life goes on and this is not a topic of major controversy. But when two pieces of software have similar names, people just can't resist commenting endlessly and upvoting this content-free bikeshedding at the expense of actual discussion.

Yes! Especially when people use an existing word like 'redshift' as their product name. (It seems to be a popular choice! I remember there also was this astronomy software for the Mac called Redshift.)

Of course, it gets even more ridiculous as the words get more common, eg see recent discussions about 'Paper' or 'Layout'

Re: Why We Chose Redshift

#34

The 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…

Because why would a company make a blog post on what color adjuster their company uses, and if they did, why would anyone care?

Re: Why We Chose Redshift

#35
post #2

Redshift is like a prison, but with excellent accommodations. It's a great platform but it pretty much the perfect example of vendor lock-in.

"Resort" is probably a better analogy than "prison." Most people wouldn't choose to leave, since the accommodations are so nice, but for the expense.

Re: Why We Chose Redshift

#36

Earlier quoted context omitted.

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.

Why not power your dashboards with it? What do you use? I am considering using a columnar data store (maybe redshift) with a BI tool like bimeanalytics.com specifically to do dashboards.

My guess is latency - using Redshift for short lived, small queries might not be the best.

Re: Why We Chose Redshift

#37
post #34

The 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…

Because why would a company make a blog post on what color adjuster their company uses, and if they did, why would anyone care?

Far weirder things have been blogged about before.

Not to mention that if you are not already familiar with the company, you probably would not know what sort of blog it was just by looking at what was presented on the HN frontpage. Could have been some random joe-schmoes blog.

Re: Why We Chose Redshift

#38

The 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…

FWIW, I didn't downvote you but you're also kind of hijacking the discussion (especially since this comment is the top comment and it really shouldn't be).

Re: Why We Chose Redshift

#39
post #26

Earlier quoted context omitted.

The UI colorizer is what I thought of immediately, too. If we took a poll I suspect the majority would be thinking of the Amazon service That's just personal projection, and is as irrelevant as an argument beginning with, "I think most people would agree that..." Personally, regardless of Amazon vs UI hack, I'm really tired of ambiguous naming in tech projects.

I'm much more tired of comments on ambiguous naming. There are at least two other people in my city who have my name, and many more who share either my first or last name. Somehow life goes on and this is not a topic of major controversy. But when two pieces of software have similar names, people just can't resist commenting endlessly and upvoting this content-free bikeshedding at the expense of actual discussion.

There are at least two other people in my city who have my name

I'm presented with information to parse about technology topics daily. Sometimes, I have to search for them and have all sorts of name collisions.

I never, ever search for information about you.

people just can't resist commenting endlessly and upvoting this content-free bikeshedding at the expense of actual discussion

One man's bike shedding is another thousand men's irritating trend. Personally, I very rarely see anyone called out for the trendy names and awful, buzzword-laden non-descriptions that infest projects.

Re: Why We Chose Redshift

#40
post #14

Earlier quoted context omitted.

If we took a poll I suspect the majority would be thinking of the Amazon service - I know I was. The date the projects were introduced isn't necessarily relevant.

The UI colorizer is what I thought of immediately, too. If we took a poll I suspect the majority would be thinking of the Amazon service That's just personal projection, and is as irrelevant as an argument beginning with, "I think most people would agree that..." Personally, regardless of Amazon vs UI hack, I'm really tired of ambiguous naming in tech projects.

It's not 'just' personal projection, nor irrelevant, if accurate. Obviously you'd have to run the experiment to find out for sure, but it's not meaningless to contribute "I would expect anyone I know to think of Amazon's Redshift first". For someone who doesn't know that others feel the opposite definition is the 'default', it might be useful to find out.
Post reply on HN