Rahul recently pointed me to a nice 1998 review of datamodels
in the database world
by Stonebraker and Hellerstein:
What comes around goes aroundThis paper is quite insightful, and I believe a good overview of the field
( Read more... )
The database people are forced to carve the database in stone. As soon as application grows big anough and there is enough amount of data to be useful, hierarchy takes over and developers are shunned away. Suddenly database is not just a mean to support the application but an entity of itself, which will be used for safety, mining and most important of all REPORTS. Then coders must have all their changes go through multilevel councils for approval to even simplest of the changes.
Comments 2
Reply
BTW The link for What comes around goes around is outdated , new one seems to be http://pages.cs.wisc.edu/~cs764-1/datamodel.pdf
cheers
Bobi
Reply
Leave a comment