[eluser]domainsvault[/eluser]
noted to the last post of mine, with everything we are doing this is serivce we are building will rely heavy on user input and the main backbone will be mySQL, there will also be high volumes of file storage from pictures and other file types. Again why the need for multiple servers comes into play. I'm no datacenter/networking engineer, so I am not 100% as how the balancing really works on the backend per say (yet). I do try to do my fair share of reading on the subjects as far as what I should worry about, and other practices other sites have used. Though just not sure how to incorporate them into the development exactly yet. But like I said in my first post. I am just curious right now, with anything I should think about putting in now to help save headache in the future when and if the time comes to expand out further. Not looking to build the end all be all solution for it, but you know something that could be considered good practice to begin with. If it we're just me I'd build an entirely proprietary MVC and forego systems like CI, Zend, other. But we are preping a team of 15 to come aboard in the next 3 weeks. So in the name of good practices as far as coding standards within our company goes we feel its best to use a system like CI
