Work for large site (PHP/MySQL)
I am creating a website with a friend, which I hope will end up being both very large in size and traffic.
It will have an online community, and most likely everything will be done by myself or my partner.
I have done a fair amount of PHP/MySQL work, but nothing too large scale.
Are there any specific things I should watch for/compensate for a larger scale project? For example, with the MySQL backend, would there be any problems? I know there is a "max connection" setting, which could possibly pose a problem unless we have access to change this on the server we choose.
Anything else that might be of some help is appreciated.
SonicMailer Pro
The best mailing list manager has just gotten better!
Click here for a full list of features!
Mark Hensler posted this at 19:06 — 22nd September 2003.
He has: 4,048 posts
Joined: Aug 2000
Right now I'm working on something rather large, and the first thing I'll say is Plan Ahead.
I didn't do enough planning and drawing (white boarding) before sitting down to write the code. I have now re-written a single form library four times. I didn't do enough planing and when I started to use this library, I kept running into problems.
The more time you spend planning, the less time you spend writting and re-writting.
Next... I have a thing for scalability. Nearly everything I write, I write to be scalable. It makes it so much easier to expand when you don't limit yourself in the design. So, work to normalize your database.
Good Luck!
Mark Hensler
If there is no answer on Google, then there is no question.
KandieMan101 posted this at 20:48 — 22nd September 2003.
They have: 140 posts
Joined: Jan 2003
I find that I do okay planning, but lack in the area of making scalable applications WELL...
nike_guy_man posted this at 21:15 — 22nd September 2003.
They have: 840 posts
Joined: Sep 2000
Mark's got most of it...
Things I forget to do:
1. Plan ahead
2. Make COMMENTS in the files... so important because I'll come back a month later and wonder what the hell that code meant
3. Save backups
4. mysql_close(). I cannot remember to put this. I'm thinking of putting it in my footer file that goes on every page but then i'd have to open on every page too
Good luck with your big project... I've been working on one for over a year now
Mark Hensler posted this at 05:14 — 23rd September 2003.
He has: 4,048 posts
Joined: Aug 2000
Nike... if you know your db link variable ($dbi = mysql_connect()), then do this:
if ($dbi) {
mysql_close();
}
ROB posted this at 02:26 — 24th September 2003.
They have: 447 posts
Joined: Oct 1999
And save them on a SEPERATE DISK! Oh lord I can't begin to describe the feelings you get when your disk with the project youve worked 3+ weeks on crashes and you have to start over from scratch. Not fun I tell you.
m3rajk posted this at 16:15 — 26th September 2003.
They have: 461 posts
Joined: Jul 2003
i had that happen once. since then i always have a remote server with a back up less than 24 hours old (if possible) my local machine copy and one on disk.. when working on a remote server, before i leave my computer for anything, even as simple as a bathroom break i pull a copy to my local machine,. and nightly back up to disk.
this way you have two copies local to you, and one remote... you're safe in almost all foreseable circumstances
POSIX. because a stable os that doesn't have memory leaks and isn't buggy is always good.
Want to join the discussion? Create an account or log in if you already have one. Joining is fast, free and painless! We’ll even whisk you back here when you’ve finished.