TAG | backcountry.com
Let’s face it, most bigger companies nowdays are afraid of trying something new. That happens with good reason — most new ideas tend to fall by the wayside, as trends normally do, and companies like to play it as safe as possible. I see new ideas and frameworks popping up all over the Twittersphere every day, and I wouldn’t consider using any of them in a production environment.
Amazon Web Services Isn’t Just a Pie-In-The-Sky
The reason I bring this up is this — Amazon Web Services in the business (not startup) world is *still* considered a new, unproven technology. And with all the marketing hype around clouds, infinitely scalable services, etc, etc, I honestly don’t blame them. It hard to believe a pie-in-the-sky promise. That’s just the point — AWS is not pie in the sky, and people that think it is need to dig deeper and understand what it is and what it offers. The fact is that Amazon Web Services has been around since 2002, and has uptime that is most likely better than your data center. Coincidentally, Amazon also knows this and is trying to eliminate the false perception that IT IS GOOD FOR YOUR COMPANY TO USE IT TOO. They published this article, along with an updated cost calculator and an Excel spreadsheet to compare your datacenter with using AWS.
Backcountry.com and S3
Ok, so the real reason for this article. At Backcountry.com, we try hard to stay as close as we can to the bleeding edge, but going into “the cloud” has always received serious backlash. That is, until recently. Earlier this month we took advantage of the cloud for the first time in a production environment: by using S3 for our “Jumbo” product images.
First, let me explain the reasons we decided to use S3. Our webapp tier, consisting of a few boxes, hosts the Interchange e-commerce framework, and also contains all our static content. The trouble was, the 900×900 images consumed about 100gb disk space, but each box only had less than 20gb left. That left us with one of two traditional options: put new hard disks in each webapp, or use our NetApp to host the images from a single location. Neither seemed ideal, since putting in new hard disks would be pricey and could take some time, and we were already short on NetApp space given the current budget. I had done some side-work using S3, and mentioned it. Chris Alef was able to push the decision as a great idea and it was agreed to do it.
Flash forward 1 week, and we were ready to go live. We were able to convert and upload the 900×900 images to S3 over the weekend, and get the UI in place in no-time flat. We have Akamai hosting edge cache in front of S3, and we had zero problems since launch last month. I asked our operations team what they thought the bill for the month would be, and they guessed $4,000. The actual bill? Under $50. Granted, Akamai probably took most of the traffic, but that’s still mighty impressive.
There’s so much more we can do with AWS, and I hope this is just the start. I hope to be able to take advantage of other AWS services such as EC2 and SQS in the future, and I think S3 helped build confidence. AWS is a service that can be relied on for both startups and established internet businesses alike.
A coworker of mine, Dustin McQuay, released the YUI Magnifier, a YUI implementation of other popular image zoom utilities. We were actually surprised to see that nothing else like it already existed for YUI, so Dustin took the challenge of building his own, with the hopes that it might be included in other larger YUI libraries.
It boasts the features:
- Display a magnified portion of an image, which is controlled by where the mouse is hovering over the image
- Control over styling
- Control over location of magnification lens
- Magnified image can be wrapped by a larger element
Though the release wasn’t very public, it was still quite an accomplishment. It happens to be one of the first open-source releases from Backcountry.com (preceded to my knowledge by only Bucardo, a Postgres replication application written for Backcountry.com by Endpoint). It was originally designed to be used for our 900×900 images, but got cut after development has essentially finished due to changed requirements.
It’s a pretty solid application, and hopefully the start of more open source to be coming out of Backcountry.com
