| From: | Aaron Optimizer Digulla |
| Date: | 3 Aug 2000 at 12:40:55 |
| Subject: | Re: AMIOPEN: Patches for bugs |
On Wed, Aug 02, 2000 at 04:53:45PM -0400, Ray A. Akey wrote:
> > And I would propose to look at JitterBug instead; JitterBug has a much
> > more simple interface and it doesn't need a database (which makes it much
> > more simple to setup, maintain and backup).
> tsk tsk.. Couldn't be more simple than it is now: "mysqldump -u <user> -p
> dbname >dbname_bak.sh" :)
Well, my last boss told me this story: He had to sort the data in a
database table. The table never changed and he added all the necessary
indexes. Sorting took about 2 minutes (ie. SQL statement with ORDER BY).
That was too slow. So he exported the whole table and used "sort".
That took 2 seconds.
Conclusion: Use a database when you need concurrency, large amounts
of data and complex data structures. For everything else, use
a directory and a set of files. FileSystems are, compared to databases,
reliable, simple to understand and use, easy to administer and lean.
PS: If you need another example then compare the speed of using
win.ini (the original way to store config information on Windows)
and the new "registry" database. Plus the reliability, stability,
ease of use, etc.