Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 1
    To be fair, there has been a movement towards No-SQL type databases which are generally more flexible than their traditional database counterparts. There are certainly disadvantages to this approach, but it does make the program the controller of its data. That said, I do think it is wrong to attempt to make a traditional database act like a NO-SQL database. Commented Sep 29, 2017 at 13:54
  • 1
    Sure, non-relational DBs have their place. But they weren't invented because the relational model was too limiting. They were used first for extremely (Yahoo, Facebook...) big data sets when relational DBs could not scale enough at all. Commented Sep 29, 2017 at 13:57
  • 1
    @Neil - I agree, but if you're going with a relational database with any kind of power, let it do what it does best. Otherwise, you have to deal with the disadvantages and get little upside. Commented Sep 29, 2017 at 15:14
  • 1
    @kilianFoth Not to be pedantic, but technically SQL databases were invented after non-relational databases. They have come back into vogue order to solve scalability (and other) problems that SQL databases have a harder time with. Commented Sep 29, 2017 at 16:00