Start Small, But Think Big

There is an interesting discussion evolving online on Web 2.0 startups and their initial planning and development.

Jeremy Wright:

It’s funny, because you’d think companies would have learned this lesson years ago. I remember back in the mid part of the .com boom I spent 2 days with Amazon optimizing their front-end code (HTML, JS, CSS, etc). Over 2 days, we trimmed about 50K of weight from it. Nothing major, just smart optimization. It saved them the need for 20 new servers and a major bandwidth upgrade.

Listen up. If your company relies on the web to stay alive, you’d damn well better be using at least some of the following “ladder to high availability”:

Backups, Redundant, Failover, Cluster, Distributed, Grid and finally Mesh

I’ll have to say I’m straddling the fence on this one. Jeremy makes sense, and he’s got loads of experience in this category. However, I really think the creator of Basecamp and BackPackIt, David Heinemeier, has a good grasp on Web 2.0 apps when he says:

Your business needs to be extremely stable, but many web 2.0 applications are social in nature, and really could be down 1% of the time with no real customer angst. That is, unless you are an essential provider (i.e. email, phone, fax, etc.). Gmail was down earlier this week, and because people depend on their mail, no matter how many times you tell them free email addresses are not reliable, you stand to lose when your company allows services like this to go down.

My suggestion is to start small, but think big.  Go ahead and create a plan that scales.  However, take into account what your business does and whether or not you really need to be more reliable than 99%.

Tags: , ,

Leave a Reply