As some of the replies have suggested, it depends very much on your application but I can talk about my experience in scaling and web hosting and you might find them helpful
Webhosting For one of my projects (http://www.borrow-err.com/), I used Webfaction and it was one of the best decision I have made. Their documentation is excellent. But if you still have questions, their customer service is really great. I have sent them emails on a weekend night and received reply within few hours, even though I specified it was not urgent. Their support for django is wonderful and I am planning to use them for all my future projects. I tried hosting images and media through amazon s3 but it has not been good. I do not have many images that needs to be served. But some times, the images take an unacceptably long time to load. I might move them to webfaction itself. Scaling In one of the applications that I am working on, I needed to scale (actually planning for the future feature.) I viewed the scaling as a two part problem, one for web page serving and the second for database. If you are using webfaction, scaling to different multiple servers is as easy as buying more hosts and copying the files to all hosts. For free, you can round robin between the different hosts. For a big price, you can also find load balancers as well. Also, memcache, which is essentially in serving web pages, can cache across multiple hosts and treat them all as one single chunk of memory. For scaling the database server, I am using the "Multiple database" (http://docs.djangoproject.com/en/dev/topics/db/multi-db/ #topics-db-multi-db) in django 1.2. I have a master which takes all the initial inputs and queries. Every 30 minutes, I replicate the content of the master to the slaves. In the future, any transaction created more than 30 minutes earlier will be sent to the slave and the rest will be sent to the master. Due to django's ability to host these slaves in different hosts, you can scale by just adding more hosts and replicating contents of the master in each one of them. Also the same host that is used for scaling web page serving can also be used for scaling databases, thus saving money. zenr -- 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.
