2 ms·
I think that back in the day, people got along fine in many circumstances without relational tables, using traditional hierarchical stores. A good solution for
by ilaksh 15y ago
I think that back in the day, people got along fine in many circumstances without relational tables, using traditional hierarchical stores.
A good solution for dealing with changing/varied schemas is to record multiple schema versions. This is the type of problem that will occur on small systems just as well as large ones, any time the requirements change, and of course how you handle those changes is a key aspect of your system design. And a relational setup has the same type of problem in keeping the requirements, schema, application and deployment in sync. I don't think I implied that there is no value in facilities for data consistency, and I did not mean to imply that a relational database cannot have some advantages, but overall for most cases my current belief is that there are more advantages, in most circumstances, especially if you are using something like CoffeeScript/Node.js, with MongoDB.