CORE Implementations

["Rick H. Wesson" <wessorh@ar.com>]

Yesterday David Kessins proposed a light weight backend database
archature. At first I didn't like his idea. So I wrote an implementation
where only the name server and domain name are managed, and the rest of the
contact data is distributed.

Below are my findings.

Distributed Contact Data
    o Easyer to manage.
    o Smaller database
    o Faster (20 Allocations a second )
    o One person could manage the system.
    o No refrencial integraty
    o Better case for a dedicated regestry business

Centralized Contact Data.
    o Larger API
    o More strict checking
    o Strict refrencial integraty
    o Regestry business will be a Value Add by ISPs
    o Costs more to manage.

Conclusion
While both are viable archatures, in the case of
distributed contact data, there is virtually no refrencial integraty for the
system. The CORE DB trusts that front end regestries to enter valid
contact data and there is no way to ensure that the contact data is
valid. Otherwize the Centralized method should be easyer to manage
and pay for.

If anyone would like to see my implementation where contact data
is distributed drop me a note and I'll e-mail it to you.

What it comes down to is basic database design, under the distributed
system there is no refrencial integraty to the system but it costs
less to run. In laymans terms the centralized regestry could not have
handles that point to objects that don't exist.

-Rick




-- 
Rick H. Wesson