NoSql vs Relational database

by

Not all data is relational. For those situations, NoSQL can be helpful.

With that said, NoSQL stands for “Not Only SQL”. It’s not intended to knock SQL or supplant it.

SQL has several very big advantages:

  1. Strong mathematical basis.
  2. Declarative syntax.
  3. A well-known language in Structured Query Language (SQL).

Those haven’t gone away.

It’s a mistake to think about this as an either/or argument. NoSQL is an alternative that people need to consider when it fits, that’s all.

Documents can be stored in non-relational databases, like CouchDB.

Maybe reading this will help.

More Related Contents:

  1. How should international geographical addresses be stored in a relational database?
  2. What is the best design for a database table that can be owned by two different resources, and therefore needs two different foreign keys? [closed]
  3. Difference between scaling horizontally and vertically for databases [closed]
  4. Relational table naming convention [closed]
  5. Best practices for storing postal addresses in a database (RDBMS)?
  6. When I should use one to one relationship?
  7. Storing time-series data, relational or non?
  8. Still Confused About Identifying vs. Non-Identifying Relationships
  9. Which is a good design for a database table that can be owned by two different resources, and therefore needs two different foreign keys? [closed]
  10. Best representation of an ordered list in a database?
  11. Minimum no of tables that exists after decomposing relation R into 1NF?
  12. NULL permitted in Primary Key – why and in which DBMS?
  13. Pros/cons of document-based databases vs. relational databases
  14. uncertainty in developing a database model
  15. What’s the difference between identifying and non-identifying relationships?
  16. Can I have multiple primary keys in a single table?
  17. Techniques for database inheritance?
  18. What is the most efficient way to store tags in a database?
  19. Microservices with shared database? using multiple ORM’s? [closed]
  20. Database EAV Pros/Cons and Alternatives
  21. What are the advantages of using a single database for EACH client?
  22. Do stored procedures run in database transaction in Postgres?
  23. Is there any NoSQL data store that is ACID compliant?
  24. Alternatives to Entity-Attribute-Value (EAV)?
  25. Is it better to use multiple databases with one schema each, or one database with multiple schemas? [closed]
  26. Is it a good idea to use an integer column for storing US ZIP codes in a database?
  27. What’s the better database design: more tables or more columns?
  28. Should OLAP databases be denormalized for read performance? [closed]
  29. Relational Data Model for Double-Entry Accounting
  30. Best beginner resources for understanding the EAV database model? [closed]

Leave a Comment