2 ms·
"Very few applications I've ever designed ever seemed like a good fit when mapped to a relational data model" I think for many applications it's sign of bad de
by fauigerzigerk 16y ago
"Very few applications I've ever designed ever seemed like a good fit when mapped to a relational data model"
I think for many applications it's sign of bad design if the data model really fits the application in the sense that application data structures have 1:1 mappings in the database. It's similar to the relationship between the UI and the underlying object model (or whatever the paradigm may be). You need separation of concerns.
Data lives longer and usually serves more than one application over time. Fitting it too closely to the needs of one particular application at one particular point in time causes too many dependencies.
Of course, there are exceptions. Sometimes applications are trivial. Sometimes data isn't analyzed or used in other contexts. Sometimes performance dominates everything else. But for most applications, the infamaous impedance mismatch is an automatic consequence of acknowledging the different requirements we have for applications and data respectively.