TechCrunch Teardown: Etsy, It's Crafty
techcrunch.com
techcrunch.com
We post fairly often in detail about the technical challenges we've had to overcome while growing the marketplace.
Perhaps this is a dumb question, but if you've already got a resize script that resizes images into 6 different sizes when the seller uploads it.
What was the reason you didn't just re-point that script at the filesystem instead of an uploaded file object? It may have taken slightly longer to process, but my hunch is that it may have compensated for man-hours you spent in building something new. What was the limiting factor there?
Why Etsy thought they had to seek new image algorithms rather than just using the ones they already used is the sort of question they very rarely answer. My analysis is that it is related to the fact that they did the processing on an Amazon server. To save bandwidth, transfer time and processing time, they sent over the medium sized images rather than the original, full size image. Of course, that doesn't explain why they decided to do it in 'the cloud' at all rather than, as you say, just operate directly on the file system, in house.
They claim to have gone through an elaborate comparison process, apparently with the visual quality comparison being done by engineers - not people specializing in the non-technical side of photography or graphics. They seem to have entirely missed the quality issue, though it was apparent enough to customers that at least a hundred of them brought it up in the forums once the switch to the new image sizes was made.
Also speaks to how irritating going into local jewelry shops was though.
Not saying it's impossible (maybe the September numbers so far support this), but the jump from ~2.1 million to ~3.7 million in 4 months feels a bit unnatural given the historical data.