HTMList.com

Last year was TechCrunch’s first shot at a demo-ish conference. Forty startups launched and presented their premise to a crowd of bloggers, journalists, VCs and such and such. Last year’s winner was personal finance tracker Mint.com. Mint allows you to sync up all of your credit cards, loans, bank accounts and even reward points and track your entire financial well-being. It creates budgets for you and makes them pretty.

The issue? Mint is really just a re-skinned version of Yodlee. Yodlee is a bank account aggregation tool that makes itself available to banks who want to offer their customers the same sort of “one look” aggregation services in a white-label manner. They’re good at what they do, and they offer a free personal edition called MoneyCenter. Mint simply slapped a bunch of pretty gradients on top of it (they actually use Yodlee as their backend) and some transaction matching algorithms that generally miscategorize items or retitle them if it thinks it knows what they were. (It’s wrong, in my experience, a staggering amount of the time.)

Read More »

Tagged with: failboat, innovation, mint, techcrunch, techcrunch50, twitter, yammer, yodlee

Posted in: Rants

Amazon has released a rather comprehensive write-up on their post-mortem analysis of why Amazon S3 went down last week. The S3 servers use a gossiping protocol to determine system states, including what servers are available and the status of the nodes across the network.

A single bit corrupted in several of these gossips such that they were still intelligible but reflecting inaccurate data about the system state. These propagated through the network (much like a virus, really) and caused most of the servers to spend most of their time gossiping or failing to complete the gossip; if the gossip doesn’t complete, the server can’t/won’t send its data.

While Amazon MD5 checksums data in containers to ensure its integrity as its being transmitted, they weren’t doing this on their gossips. They’ve since established several new practices to attempt to ensure that a problem like this won’t cause a failure across the entire system, including better failure handling with gossips and faster restoration when nodes do go down.

They end their missive simply enough, owning up in a way I give them credit for:

Though we’re proud of our operational performance in operating Amazon S3 for almost 2.5 years, we know that any downtime is unacceptable and we won’t be satisfied until performance is statistically indistinguishable from perfect.

“Statistically indistinguishable from perfect” is a rather poetic phrase, and I’d like to think we strive for that over at Synapse Studios. But my stats-masters programmer would just mock me.

Read their full statement here.

Tagged with: amazon, amazon aws, amazon outage, amazon s3, failboat, gossip, post-mortem, s3, statistics

Posted in: Tech News