Hi All,
I recently asked around for suggestions for anew system build, I think my requirements are similar to those of @canadiancreed. I also have a very large amount of files, mainly photos, video clips and music, and also a whole bunch of application files I've been playing with, these are currently backed up to my sever file as well. Another similarity is in our coding requirements. I need a system that can handle AMP stacks and manage running multiple VMs/app servers, and who know what I'll need to handle in the future, so I wanted a certain amount of flexibility.
Anyway, I actually ended up ordering the almost exact system. One exception - I invested in Asus Xonar DG audio card - as a music fan, this was important to me.
Still, I have some issue I need some input on - I will probably begin working on a project that will require comprehensive database management capabilities. I want to have the ability to handle MySQL database scalability issues as the database grows, and do this remotely if needed. Since the database in question is pretty big already and will most likely continue growing, and fairly quickly. What I'm not sure about is what method to use to scale the database - partitioning or MySQL sharding. I found this nice comparison between MySQL sharding and partitioning that was a nice read, but has helped me decide. If any of you have any experience, advice, or tips for me, I'd be oh so grateful.
Rona