NoSQL in one machine

As part of my university curriculum, I completed this project, which is to help the company move from its relational data warehouse to NoSQL data warehouse. The fact is that what they are looking for is the best performance in large workstations, but so far they have used the same machine, and if they really switched to NoSQL, they still want to use the same machine for cost reasons.

As far as I know, the whole point of NoSQL is to run it in a large distributed system of several machines. Therefore, I don’t see the point in this migration, especially because I am sure (but not completely) that if they install NoSQL, they will probably have worse performance.

But I still don’t like to tell them about it, since I'm still new to this area (less than a month), so I wonder if there is a situation when using NoSQL in one machine for a data warehouse will be justified performance wise? Or is this just a bad idea?

+4
source share
3 answers

The answer to your question, as well as the answer to so many questions, "it depends."

, , . , , .., . , SQL/ , , concurrency. . SQL .

no-sql, , " ", . , . . , , sql , ( SQL , NoSql).

, no-sql. Mongo, Elasticsearch Couchbase (, ) SQL- . .

+1

, , . , cassandra. hbase, node. api json, dbs , couchbase, mongo db. , nosql

+1

, , , MongoDB. , - . , . , .

MongoDB, Oracle, SQL Server, MySQL, SQLite HBase. , , . MongoDB . - . , , .

NoSQL RDBMS, , :

  • RDBMS
  • MongoDB , (, - )
  • .
  • , , , , - .
0

Source: https://habr.com/ru/post/1527905/


All Articles