Skip to content

Comment on Where/How are you hosting your Facebook App?

Comments

This is a hard problem.

If your app isn't successful then there's nothing to worry about.

But what if your app is super successful? How would you ever be able to secure enough servers to meet the demand without burning a very deep hole in your pocket?

What we need is a Y-Combinator like incubator for Facebook Apps - a company which will host your app and help you scale it up for a chunk of equity.

I don't think it would be smart to include hosting in an incubator. We made a conscious choice not to.

(a) Economically hosting is a commodity. It's not an area where we can add any special value. We don't do hosting for the same reason we don't supply office or living space: it's better for founders just to buy these on the open market.

(b) Hosting is a technical problem, which it's good for founders to have to solve. We're happy to deal with all the paperwork of incorporation, because you really don't have to know about that stuff to run a company. (I haven't read half our legal documents myself.) But startups do have to understand how to manage servers.

I think EC2 ( http://aws.amazon.com/ec2 ) is a pretty good way to go but I'm interested in what others are thinking.

EC2 is not suitable for most Web applications:

- You don't get a static IP address, so if your instance fails and needs to reboot, you might end up with a different IP address.

- If your instance fails, it also loses all the data stored in it.

- There is no hardware load balancing.

With that said, you can probably use it to complement your other servers by doing some of the batch processing.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.