On 8/5/2010 7:53 AM, cootetom wrote: > Is it better to have one large database with all the data for a web > site in it or many smaller databases that hold data for specific > area's of a web site in it? > > Thinking that one database with some sort of clustering technology is > better than trying to manage many smaller databases? > I'm not sure why clustering technology would be necessary to support a single database ...
Most database engines (including MySQL, PostgreSQL and MS SQL Server) will allow a single instance to support multiple databases if you need that. There isn't really any reason why you should have separate database for a single site, though. What advantage would you perceive to this? Were they going to be on distinct server machines? > Also, if data needs to be linked should multiple databases be avoided > all together? > It's certainly going to be slow to join data from tables in two different databases, and you may end up having to do this in your application code. > > Asking these questions because I've not faced the issue of scaling > massively as yet and would value the knowledge from those who have. > Define "massive". It's usually best to start with one database, and optimize as the load requires. Otherwise you might find yourself optimizing areas where performance is already adequate. regards Steve -- I'm no expert. "ex" == "has-been"; "spurt" == "drip under pressure" "expert" == "has-been drip under pressure". -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
