I'm not certain I understand what you're asking because high available
isn't exactly related to distributed systems. I think you're asking
about sharding (partitioning of data across multiple databases). If
that's your question, then the answer is yes, it can be done. It's
just writing a custom backend, tweeking managers, etc. The deep
truth is, however, that all you would be doing is building the Google
App. Engine. The question is why not start there.
As it turns out, twitter is not an example of decentralized
distributed system though ("We currently use one database for writes
with multiple slaves for read queries" ~
http://blog.twitter.com/2008/05/its-not-rocket-science-but-its-our-work.html).
Their problems aren't really related to a lack of sharding as much as
they are querying on a many-to-many model I think. There's a good
blog out there on the problem but I can't find the link.
On Jun 7, 7:11 am, lgr888999 <[EMAIL PROTECTED]> wrote:
> Im curious to hear if theres any django developer that has built any
> decentralized distributed system with help of django? I know building
> a website doesnt include any scaling problems in the beginning, im
> asking more out of personal interests in high availability. If you
> dont have any experience with it feel free to post your thoughts of
> how you would build a huge decentraliced system. Now of course it
> would depend on what the purpose of the system is so lets just take
> twitter as an example. :)
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
