Multiple MySQL databases to avoid too many connections?

I've got a site I'm working on right now, and I want to make sure there will be no database errors when the site gets a ton of traffic... I've got two sets of data that would normally just go in two different tables...

Would it be better to put them in separate databases, instead of just separate tables, to lighten the load when the site gets pounded with traffic?

Thanks

 

How big are your two datasets going to be?

 

won't make any difference putting them in another database. The two databases would still be run via the same MYSQL server so performance limit is still the same. If you're really expecting a ton of traffic then you should look at a mysql cluster.

 

Ah this is the fun stuff

Unless you are expecting a mountain of traffic, and i mean millions and millions, of page views a day you wont need 2 databases for production. Keep your database for all writes and use caching to lighten the load for reads

Read up on memcached : www.danga.com/memcached/

You can pull data from your database, and then store it in memory so next time you need it you dont have to hit the database again.

The other option is to use MySQL replication and spread your reads over 2 servers.

Hope this helps

 

Awesome guys, rep added, thanks for the help...

I'm going to look into "memcache"... I'm not worried about the site getting too much consistent traffic, but more worried about "traffic spikes"... Thanks again...