libertyct Posted June 26, 2007 Share Posted June 26, 2007 Hie guys, im a newbie here but not a complete newb to php coding . I recently got hired in a small firm as a web dev primarily in php and a little asp.net. Now my boss has informed me that i will be responsibe for coding a course registration system that could end up handling upto 10,000 people. I know how to code the functionality e.t.c. but i have never worked on a system that would have to support 10,000 people. Are there any tips you guys could share about building these scalable apps, maybe issues with bandwidth? database design? etc thnx libertyct Link to comment https://forums.phpfreaks.com/topic/57288-so-i-just-got-hired-large-scale-app/ Share on other sites More sharing options...
The Little Guy Posted June 26, 2007 Share Posted June 26, 2007 - try to store as much info into sessions as possible, this will be less stressful on your database. (Do the least amount of querying as possible) - keep images to a minimum file size - if you have passwords, and are using a mysql database, use the mysql PASSWORD() fuction Link to comment https://forums.phpfreaks.com/topic/57288-so-i-just-got-hired-large-scale-app/#findComment-283177 Share on other sites More sharing options...
per1os Posted June 26, 2007 Share Posted June 26, 2007 I dunno why the PASSWORD() function is ideal for 10,000+ users, MD5 works great. But key is Index the columns that you query on the most, IE: if you pull users by username, and email. Index username and email. That will speed up the DB and keep it running smooth. Bandwidth should be fine as long as your not dishing out absurdly huge files. Do not store images in the db, store them on the server. Making the most out of each query you run works the best. So if you do have the DB in 3NF form, and you can reference the users, user_settings etc in one query, best choice is to do it that way. Anyhow hope that helps. Link to comment https://forums.phpfreaks.com/topic/57288-so-i-just-got-hired-large-scale-app/#findComment-283206 Share on other sites More sharing options...
Wildbug Posted June 26, 2007 Share Posted June 26, 2007 Don't use MySQL PASSWORD() for your own password authentication scheme (having repeated this ad nauseum). The function is for MySQL's own user scheme and can change at any time. Use MD5() (good) or SHA1() (better). Link to comment https://forums.phpfreaks.com/topic/57288-so-i-just-got-hired-large-scale-app/#findComment-283242 Share on other sites More sharing options...
libertyct Posted June 26, 2007 Author Share Posted June 26, 2007 thanks very much guys. any thoughts on MyISAM vs InnoDB? Link to comment https://forums.phpfreaks.com/topic/57288-so-i-just-got-hired-large-scale-app/#findComment-283284 Share on other sites More sharing options...
per1os Posted June 26, 2007 Share Posted June 26, 2007 Never used transactions with MySQL so I always used MyISAM. I guess if you want to be able to rollback etc I think innodb is it, if not than myisam. Link to comment https://forums.phpfreaks.com/topic/57288-so-i-just-got-hired-large-scale-app/#findComment-283290 Share on other sites More sharing options...
libertyct Posted June 26, 2007 Author Share Posted June 26, 2007 thnx again Link to comment https://forums.phpfreaks.com/topic/57288-so-i-just-got-hired-large-scale-app/#findComment-283312 Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.