Re: [Bug-gnupedia] Architecture Questions

[Bryce Harrington]

On Sun, 21 Jan 2001, [iso-8859-1] Rob Scott wrote:

> but in C),  if the db goes down the system becomes
> unsearchable,  which makes it effectively useless,
> unless the user wants to remember the uid# of each
> file you need.
> This was something that came up when me an Thom were
> figuring out our  ``proposal'', but we decided against
> it for just this reason.

It is unsearchable only until you've regenerated it from the original
files.  (Yes, that is annoying, but database corruption is not a very
frequent occurance.)

> --- Bryce Harrington <address@hidden> wrote: > On
> > C)  Hybrid.  An index is generated from the original
> > files and fed into
> > the database.  The database is used for doing the
> > searchin' stuff, and
> > the original files used to provide the complete
> > info.
> > 
> > I favor C.  This is probably clear.  A is sufficient
> > initially, and I
> > would support it from a starting point, however it
> > will not scale well.
> > B is ok in theory, however databases do have limits,
> > and they do crash
> > from time to time, and putting all faith in them is
> > unwise.  Databases
> > are good for doing indexing and searching.  File
> > systems are good for
> > storing.  Let each do what it does best, IMHO.

-- 
Bryce Harrington  ~  ACME General Purpose Hacker / Designer / Rocket Scientist
------------------------------------------------------------------------------
SBL SBIRS/Low NPOESS NGST  HarrGene CivII WorldForge Eidetic Circe STAGE iMSDW
bharrington @ msdw.com     bryce @ neptune.net     bryceharrington @ yahoo.com