Media Dojo

Time for the second installment of last week’s Amazon Web Services (AWS) meeting for local start-ups in Seattle. Rounding out the four customers presenting last Thursday were two Seattle-based media plays, nuTsie and Zumobi.

First up was Bob Wise, VP of Engineering of nuTsie, (www.nutsie.com), which allows people to port their iTunes play list across web and mobile platforms, including Blackberry and iPhone.  Basically, nuTsie takes a user’s existing iTunes library and rolls it into a streaming service much like Pandora. They don’t use the actual music in the library but the meta data about the songs and/or a playlist to create a super customized experience anytime, anywhere. If it seems a little disjointed there is method to the madness. Music licensing remains a mess even after a decade of industry tinkering. Like Pandora, Melodeo must make all its music streaming DCMA compliant so legally nuTsie is considering web radio rather than a a formal music distribution service.  The primary outlets are streaming for the web and for mobile phones. The business model is based on advertising for web streaming and subscriptions mobile phones.

For plumbing, Melodeo uses Amazon S3 to store and serve up the audio files (several TB in aggregate) that stream via a Flash player. The web-based nuTsie service gets about 10 million page views per month with about 10,000 hours of streaming music content served up each day between the web and mobile components. Both the streaming service and the mobile play are hosted on AWS. Bob said that for a typical load, it takes about 40 EC2 instances (think 40 virtual servers) that are about evenly split between large and small instances with one extra large instance for the main database. If you do a back of the envelope calculation it works out to roughly $10-15 per hour for pure compute capacity. Remember that nuTsie is also paying for data and certain transfer bandwidth charges.

source: http://aws.amazon.com/ec2/#pricing

One aspect of Bob’s presentation I liked was how he illustrated the effect of business forces on technical design. Chris Anderson of Wired fame used music as exhibit A of his Long Tail hypothesis. Bob said that in his experience the long tail might be long but it’s also thin as fishing line. Basically, this means that ultimately the number of music plays instead of the number of music tracks is what makes or breaks the business. Given the fact that the action stays with a relatively small number of tracks, nuTsie uses Amazon S3 as a content delivery network (CDN). If it sounds strange to use a data storage service to serve up content, take a look at charging. With many other CDNs in the market, a business is charged according to how much data sits at the edge node plus the transfer bandwidth to the end user. Thus, the key cost point is how much you get charged for keeping music tracks in storage which aren’t being played very much. Sticking several TB of music data out there on various edge nodes is an expensive way to do things. If you look at parking data similar to parking cars, loading rarely played music or video on an edge node is a bit like using a parking meter or a temporary lot whereas oft-played content needs the equivalent of a monthly reserved space. It’s an imperfect comparison I know. However, it’s decently clear that some of the heavy lifting for media providers is to figure how thick is the head of their demand model and how thin is the tail. Otherwise, it’s money out the door, cloud or not.

Comments are closed.