Why NoSQL is better at “scaling out” than RDBMS?

by

So I’ve been trying to figure out the real bottom-line when it comes to NoSQL vs RDBMS myself, and always end up with a response that doesn’t quite cut it. In my search there are really 2 primary differences between NoSQL and SQL, with only 1 being a true advantage.

  1. ACID vs BASE – NoSQL typically leaves out some of the ACID features of SQL, sort of ‘cheating’ it’s way to higher performance by leaving this layer of abstraction to the programmer. This has already been covered by previous posters.

  2. Horizontal Scaling – The real advantage of NoSQL is horizontal scaling, aka sharding. Considering NoSQL ‘documents’ are sort of a ‘self-contained’ object, objects can be on different servers without worrying about joining rows from multiple servers, as is the case with the relational model.

Let’s say we want to return an object like this:

post {
    id: 1
    title: 'My post'
    content: 'The content'
    comments: {
      comment: {
        id: 1
      }
      comment: {
        id: 2
      }
      ...

    views: {
      view: {
        user: 1
      }
      view: {
        user: 2
      }
      ...
    }
}

In NoSQL, that object would basically be stored as is, and therefore can reside on a single server as a sort of self-contained object, without any need to join with data from other tables that could reside on other DB servers.

However, with Relational DBs, the post would need to join with comments from the comments table, as well as views from the views table. This wouldn’t be a problem in SQL ~UNTIL~ the DB is broken into shards, in which case ‘comment 1’ could be on one DB server, while ‘comment 2’ yet on another DB server. This makes it much more difficult to create the very same object in a RDBMS that has been scaled horizontally than in a NoSQL DB.

Would any DB experts out there confirm or argue these points?

More Related Contents:

  1. Difference between scaling horizontally and vertically for databases [closed]
  2. NoSql vs Relational database
  3. MAX(), DISTINCT and group by in Cassandra
  4. Is nosql Database good for Online Money Transaction management [closed]
  5. What does Redis do when it runs out of memory?
  6. Cassandra port usage – how are the ports used?
  7. What is the difference between CouchDB and Couchbase?
  8. NoSQL Use Case Scenarios or WHEN to use NoSQL [closed]
  9. Why isn’t RDBMS Partition Tolerant in CAP Theorem and why is it Available?
  10. How to do basic aggregation with DynamoDB?
  11. NoSQL: Getting the latest values from tables DynamoDB/Azure Table Storage
  12. How to write denormalized data in Firebase
  13. MongoDB: How to update multiple documents with a single command?
  14. Is there a query language for JSON?
  15. Firebase data structure and url
  16. Scalable Contains method for LINQ against a SQL backend
  17. TRIGGERs that cause INSERTs to fail? Possible?
  18. Best data store for billions of rows
  19. Querying DynamoDB by date
  20. Searching in Firebase without server side code
  21. Storing images in NoSQL stores
  22. MongoDB lookup when foreign field is an array of objects
  23. Non-Relational Database Design [closed]
  24. Algorithm for autocomplete?
  25. Has Django served an excess of 100k daily visits? [closed]
  26. Should I normalize my DB or not?
  27. RMySQL dbWriteTable with field.types
  28. What’s the correct name for an “association table” (a many-to-many relationship) [closed]
  29. Unique IDs with mongodb
  30. How to get the byte size of resultset in an SQL query?

Leave a Comment