Basic Database Considerations
A friend asked me what database to use for a small one-page vendor listing page that will hopefully become popular and grow very large. The vendors, at least in the beginning, will be adding their own listings.
Here is my reply:
The basic mechanism will be similar regardless how small or big the site is. In essence: Data In. Data Stored. Data Out.
Data Stored is the central item.
Data In sends data to Data Stored.
Data Out gets data from Data Stored.
Data In and Data Out operate independent of each other, but each depends on Data Stored.
Therefore, Data Stored is the most important of the three.
Without Data Stored, neither of the others work. With Data Stored, either Data In or Data Out can be down and the other will still hum right along.
Deciding on a database mechanism for the long term is important. The database mechanism might be changed down the line, but if that is done both Data In and Data Out need to be modified, essentially rebuilding the system from scratch.
With a solid database mechanism in place, Data In and Data Out can be modified as needed without affecting the other parts of the system.
OK, I'll get off the pulpit now :)
I recommend standard MySQL. Some will argue other SQL systems are better. And they may well be. The reason I recommend MySQL is that MySQL is readily available at virtually all good hosting companies. If a server move needs to be made, the data can be exported from one, imported into the other, and it's good to go.
Hm, I did say something about getting off the pulpit, right? Well, OK.
[stepping down]
Will Bontrager
