I have lately used Django for any really small Content management systems-style website. I had been so impressed with how fast and simple it had been to build up a Django project, that I am now thinking about utilizing it for any considerably bigger project.

However, before I recieve looking forward to the concept, I simply desired to run it by somebody that really is promoting a really large Django website (with lots of features, and traffic).

Baring in your mind that lately I have tried personally mostly C# Asp.Internet - What are the issues I ought to learn about?

I discovered this very worthwhile to see: http://softwaremaniacs.org/blog/2008/02/24/why-offline-crashed-en/

You will find lots of interesting articles within this blog, but, regrettably, they are all in Russian.

Added: And also, since that publish Ivan did write MySQL after sales supporting master-slave replication: http://softwaremaniacs.org/soft/mysql%5Freplicated/en/

It is going to depend a great deal on precisely what you mean by "large" and "complex".

So far as "complex", have a look at Pinax. A lot of features all built from simple Django applications hooked together and it is still considered a framework that you'd use to start with towards creating a social software site. But I am sure you are able to still develop some version of "complex" that does not mesh well with Django's architecture.

Handling considerable amounts of traffic and enormous datasets is really a different matter. Ultimately, if you achieve big enough, Django's not likely to handle it. However ,, neither will any framework. Jacob-Kaplan Moss (among the django devs) has an excellent article setting out a brief history of web design that brought as much as where Django is. He constitutes a pretty strong situation why Django or other framework can't stand out at both rapid development and massive scalability why will still be worth beginning with one. Essentially, no two high traffic sites will have exactly the same scalability issues: everyone will require a custom approach that's specific towards the exact kind of data and traffic they suffer from. Consider it's difficult to calculate wherever individuals bottlenecks will be, it's wise to begin with an immediate development framework and begin changing components whenever you encounter the requirement.

As pointed out, it is dependent on which "large" and "complex" really mean. If you are thinking about building another eBay, the reply is "most likely not".

This is requested a lot. Frankly, you will find lots of solutions available. This thread is fairly good. There is additionally a perfectly attended presentation at DjangoCon this season on Scaling Django. The choice is yours to architect your website to ensure that it scales, no matter what technology you utilize.

My answer could be: If your internet site is likely to outgrow Django (or other framework, for your matter), it's huge success and you will most likely have sufficient capital to employ a gigantic team to rewrite the whole factor.