Should I Split Tables Relevant to X Module Into Different DB? Mysql
Posted
by Michael Robinson
on Stack Overflow
See other posts from Stack Overflow
or by Michael Robinson
Published on 2010-06-14T14:38:36Z
Indexed on
2010/06/14
14:42 UTC
Read the original article
Hit count: 199
I've inherited a rather large and somewhat messy codebase, and have been tasked with making it faster, less noodly and generally better.
Currently we use one big database to hold all data for all aspects of the site. As we need to plan for significant growth in the future, I'm considering splitting tables relevant to specific sections of the site into different databases, so if/when one gets too large for one server I can more easily migrate some user data to different mysql servers while retaining overall integrity.
I would still need to use joins on some tables across the new databases.
Is this a normal thing to do?
Would I incur a performance hit because of this?
© Stack Overflow or respective owner