I guess I'm asking if there's any inherent reason to *not* use Django for a website that you hope/anticipate will have many simultaneous users and high levels of database reads/updates. And, related, what's the most "extreme" Django deployment currently out there.
And on the database side, what database do folks recommend for the more extreme apps. Can mysql go all the way or are there limitations there too? On Mar 24, 9:34 pm, Alex Gaynor <alex.gay...@gmail.com> wrote: > On Wed, Mar 25, 2009 at 12:32 AM, ldm999 <malcolm.le...@gmail.com> wrote: > > > Is there any reason why Django couldn't be used to create a website > > that gets Facebook-like traffic? > > Not really, at that point it's mostly scaling your DB(since web nodes are > comparatively easy). Django doesn't have a public API for mulitple > databases so it could be harder, but there is both private APIs and external > tools like PgPool. > > However, what's the real question you're trying to answer? 100% of websites > don't get traffic that approaches facebook. > > Alex > > -- > "I disapprove of what you say, but I will defend to the death your right to > say it." --Voltaire > "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
