February 9, 2007
Do modern databases have too many tables?
Mike Robinson thinks modern databases have too many tables. However, I’m not sure about his argument. He argues that more tables = more code, but is that really true? Or are they just a good framework from which to modularize code? Some of his specifics might be perhaps addressed by updatable views. And other of his complaints were about performance hacks (caches, history tables), that have little to do with database normalization.
Frankly, the kind of application he describes is one I think should be bought from a third-party vendor, who probably should indeed use lots of tables. I agree that relational fundamentalism is way overblown, but perhaps for different reasons than Mike does.
Categories: Theory and architecture
Subscribe to our complete feed!
Comments
Leave a Reply