In one of youtubes videos about scalling web sites I found the statement that, however, in term of scallability, noSql is easier and more flexible, though it is better to use SQL for data important enough to not want them be lost (not necessarly secure). Why is so? What mechanism make SQL safer in such term? I'm very VERY beginner with databases so easy answers will be appreciated.

closed as too broad by gnat, Dan Pichelman, TZHX, Robert Harvey, Robbie Dee Jul 20 '16 at 15:37

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    "NoSQL" is a very broad term. "SQL" refers to a specfic language that clients use to interact with a DBMS. It implies certain capabilities, and it requires that data be organized in a specific way. "NoSQL" literally refers to any data storage system that does not use the SQL language (or, does not only use the SQL language). Attributes like scalability, reliability, security, etc. depend much more on any given implementation than on any specific access language. – Solomon Slow Jun 28 '16 at 16:26

I guess what your sources are refering to is ACID compliance. There are lots of SQL databases which provide ACID. Most NoSQL databases, however, do not provide this for the sake of better scalability. Here is an article on Quora which might give you an explanation.

For both categories of databases, however, if one wants data not to get lost, regular backups are important, and that has nothing to do with "SQL" or "NoSql".

Not the answer you're looking for? Browse other questions tagged or ask your own question.