Skip to main content

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.

Required fields*

3
  • 3
    If you can't see a performance boost, that's what you say. Fact is that most of the NoSQL solutions forgo one (or more) of the ACID properties of a relational database, so they do less. Commented Nov 12, 2012 at 9:58
  • 1
    There are some workflows (and data structures) that can't easily be mapped to a traditional ACID-enabled relational database. For those, you can see huge performance increases by using a NoSQL database. If, however, you simply take an existing (well-designed) SQL DB and put it into a NoSQL Database, then your performance will surely suffer. Commented Nov 12, 2012 at 9:59
  • 2
    The answer is: Has it been established as faster? And faster in what? Development time? Read time? Write time? Which type of write? What are we comparing it to? Multi-table queries? Joins? Commented Oct 29, 2017 at 12:01