"Fast" is extremely relative, and has nothing to do with scalability. A "slow" web site can still scale to millions of users, and a 'fast" web site can go down with only a few thousand hits.
First off, what type of application is it? Many reads, many writes, or both? If you have lots of reads and few writes (like a blog or PR site), you can do heavy caching and you'd be fine with just about any host. If you have lots of writes (like a forum or community web site), then more thought is going to need to be put into the process. Second, how scalable do you need the application to be? How many requests per second are you expecting? Chances are you're not going to create another Twitter or Facebook. You need to think about how to estimate this before you even build the application. If you get 10000 users a day, but they're evenly spread out, then that's one thing. However, if you're getting 10000 users all between 12pm and 2pm EST, then that's quite another. Chances are your application doesn't need to be as "scalable" as you think it needs to be. Now it sounds like you're very new to all of this. I would suggest getting a basic version running on your local computer - Apache, mod_wsgi, and postgresql, if that's the way you want to go. Once you have a working setup, you can decide how to proceed from there. You don't want to make configuration errors when you're paying for a bandwidth bill. :-) Report back with some of this information once you've gotten a general feel for your needs. I know "scalable" has become quite a buzzword lately, but don't let it steer you in the wrong direction. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
