> First off, what type of application is it? Many reads, many writes, or
> both? If you have lots of reads and few writes (like a blog or PR
> site), you can do heavy caching and you'd be fine with just about any
> host. If you have lots of writes (like a forum or community web site),
> then more thought is going to need to be put into the process.
In addition to tiemonster's good list of stuff, it might help to
know some characteristics of your requirements. If seeing
one-true-data-set isn't a must-have, you have a little extra
breathing room -- e.g. Twitter/Facebook type apps, it doesn't
matter if my tweet/post isn't *immediately* visible to
*everybody*, if it takes a little while to percolate across
various databases to eventually become consistent. On the other
hand, if you're developing a banking application, you better be
sure that all instances are viewing the same data.
-tkc
--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment