All geek questions in one place

NoSQL Movement - Rationale for SQL RDBMS

Last year I did a lot of projects with NoSQL json based databases - rich (not key / value repositories), such as CouchDB, MongoDB, RavenDB. I often talk with other programmers about my adoption, I notice that I am always added: “Of course, the SQL RDBMS system is still there, always the best for a specific project / task” - this is not visible as a small disclaimer as a lover of the fist, however its rather shallow expression. Beyond legacy projects that already have an RDBMS investment or corporate mandate that insist on Oracle, I'm struggling to come up with some future green field project that I would choose for an SQL database. Its CouchDB is completely for me, as far as I can see with a rich map / zoom, changes the channel,replication support, RESTFUL api (sorry to sound like a plugin)

I would like to hear those that “get” (outside of screencasts) NoSQL Json M / R databases, such as CouchDb, what types of projects you think you will use MS-SQL, Oracle, Postgresql, etc. in future?

thank

+3
source share
2 answers

One of the strengths of SQL is that there is a standard way to model just about anything — it may not provide the optimal solution for any given project, but it does provide a reasonable opportunity. This means that in a corporate environment, you can decide that everything will be stored in Oracle to get the benefits of service from a single system without the risk that it will be completely inappropriate for future projects.

, , , - -, .

NoSQL , SQL. SQL -, , . NoSQL , - , , . , . , , . , , , .

, , , NoSQL , . , - , , , .

- , / , , - NoSQL .

+4

, , , . , . (, Google, ), NoSQL - . .

/ , -, -, . NoSQL.

+2

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

More articles:


All Articles