This is not a question like NoSQL and SQL. I'm interested in types of scenarios in which you can use a combination of a DBMS and a NoSQL database, and using the combination is well suited . In general, I understand that "it depends" on the situation and the task, but I think that there should be some general / general situations 1 where this combination is very useful.
Each of the above types of solutions has its own strengths and weaknesses - what I work for is situations / scenarios in which the strengths of both can be fully used and used.
In my opinion, you can be e-commerce. Payments, Transactions, etc. On the RDBMS (think ACID 2 ), as well as product information and directories in the NoSQL database. But is it suitable?
Problems with application cross-connections, for example. As another example, the logbook is probably well suited for a solution such as NoSQL.
Alternatively, why don't you use both of these types of technologies in combination?
Edit: I just repeat, I understand that SQL and NoSQL have their inherent advantages and disadvantages and that some types of situations are more suitable for only one of the above data stores.
1 I know that giants such as Facebook, Google, etc., probably use a combination of them, but in most cases most of them work, but almost all of them make such huge decisions. More typical everyday stuff.
2 RavenDB is a NoSQL solution supporting ACID transactions
source
share