0

Right upfront the title looks like a possible duplicate, but it is not, since stackoverflow answers only answer at a high level of abstraction, this is about internals. Furthermore most of the diffences are not even true because most of them are just features that can be implemented in both as I have read. I'm have a bit knowledge about sql and sqlserver, if I say something wrong in the following statements please correct me.

To clearify with high level of abstraction it is among other things meant that people write nosql does not support this and that. Even if nosql is capable of supporting that feature. Of course some of the nosql-dbs then also support then that feature that is claimed to be not supported by nosql. It looks like nosql and sql are quite similar internally so that it's only a question of which featureset the db does choose to support.

question 1: Is there even a difference between them internally except sql enforces rules and has more features?

It looks like nosql and sql is the same except nosql just does not have advanced features like sqlserver. Both store metadata. NoSql is often referred as keyvalue pairs json syntax. I don't know about the internals of sql, but it cannot be so different since it's just metadata, can be xml, json or some other syntax. Tables also have to be stored in some kind of metadata syntax I guess.

Both have a program that can resolve querys and return something.

Obviously when you drop a whole featureset you get a performance boost like nosql.

question 2: Why should sql scale worse then nosql? They are quite similar internally. Maybe it's just that the current rdms have implemented scalability of the huge featureset not very good because it's not quite simple?

Community
  • 1
  • 1
  • 2
    This is too broad. NOSQL databases cover a wide variety of technologies. However, your second question is easy to answer. SQL (really relational databases) enforces ACID properties; these are (relatively) expensive on parallel systems. NOSQL often relaxes the ACID properties (e.g. "eventual consistency"). If you have fewer guarantees, you can be faster. – Gordon Linoff Jun 14 '17 at 19:39
  • I have read that there are also nosql dbs around that support ACID –  Jun 14 '17 at 19:44
  • "[Y]ou get a performance boost" *where* you boost the performance. Some features are boosted, others are degraded. That means dropping code and/or different code. [But "NoSQL" is a grab-bag term so details depend on each system.](https://stackoverflow.com/a/44212536/3404097) Nb your "internal" features are so general that they are just external features. Which, of course, must be implemented somehow, but not similarly. PS Sometimes you are very unclear. Your second paragraph is especially unclear. Please edit to clarify. (Simplify sentences; make referents clear; forego sentence fragments.) – philipxy Jun 15 '17 at 09:56

0 Answers0