Codd emphasised the relational model as being able to change the underlying storage representation without breaking apps. Will this eventually be a problem for

Codd emphasised the relational model as being able to change the underlying storage representation without breaking apps. Will this eventually be a problem for NoSQL? Or, is the scalability worth the sacrifice? Or, does NoSQL typically have only one (main) app, so making it work with a specific storage representation is not a big deal? The relational use-case was many different apps, with different versions, needing different access paths to the data. But if you just have one known set of access paths (like a REST URI), you can just design the DB for that. Hierarchical databases worked well when just one DB, one app; they just weren't very flexible. Hierarchical databases are fast and simple but inflexible as the relationship is restricted to one-to-many, only allowing for one parent segment per child. http://it.toolbox.com/wiki/index.php/Hierarchical_Database http://it.toolbox.com/wiki/index.php/Hierarchical_Database