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
On Sun, Jun 8, 2008 at 2:11 AM, lgr888999 <[EMAIL PROTECTED]> wrote:
> 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. :)
>
It's easy. All you have to do is to avoid all single points
Great write up! Thanks! Im fully aware of that the problem is in the
datastorage but django doesnt support for example sharding or multiple
databases out of the box, the other way around its more about keeping
things dry and normalized which makes it harder to build something
decentralized. Hence
lgr888999 wrote:
Great write up! Thanks! Im fully aware of that the problem is in the
datastorage but django doesnt support for example sharding or multiple
databases out of the box, the other way around its more about keeping
things dry and normalized which makes it harder to build something
dec
replication isnt exactly distributing... with only one master db which
handles all the writes you have a single point of failure...
On 7 Juni, 20:05, Jeff Anderson <[EMAIL PROTECTED]> wrote:
> lgr888999 wrote:
> > Great write up! Thanks! Im fully aware of that the problem is in the
> > datastorag
On Sun, Jun 8, 2008 at 7:57 AM, lgr888999 <[EMAIL PROTECTED]> wrote:
>
> replication isnt exactly distributing... with only one master db which
> handles all the writes you have a single point of failure...
In MySQL and very likely in other DBs you can have a multi-master setup with
more than on
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
Pat: Im pretty sure you can build a twitter clone with django and make
it scale pretty well with replication but you still have a single
point of failure if the master db gets to much load. Im thinking
about simpleDB from amazon. I wonder if that would be a good platform
to build something twitte
Twitter isn't a good candidate for simply creating a cache and replicating
your database. I'll just post a link, since it goes along with my own
thoughts.
http://ayende.com/Blog/archive/2008/06/03/Architecting-Twitter.aspx
On Sun, Jun 8, 2008 at 12:32 PM, lgr888999 <[EMAIL PROTECTED]> wrote:
>
9 matches
Mail list logo
