NoSQL - application features

Question

NoSQL

In what case is it justified to use databases such as MongoDB, CouchDB, Redis and some others?

Does it make sense to put them instead of the classic mysql, on a site with a low load?

Are they used in conjunction with mysql, or do they work separately?

Answer 1

We have a huge distributed project. Users, roles, various metadata - in mysql, everything else - in couchdb.
Life is very good.
CouchDB views allow you to make your application incredibly flexible without spending time thinking through complex internal relationships, creating composite indexes in the database, etc.
And due to very convenient administrator tools (amazing web admin panel) and master-master replication, we connect an additional server to the system in literally 20 minutes (100+ requests per second, several gigabytes of data, 2 servers).

Answer 2

IMHO still damp, in principle, you can put it on sites with a weak load, purely out of interest, dig deeper, imbued with the concept.

Answer 3

"Overview of NoSQL systems" is exactly what you want to know.

Answer 4

As a CouchDB user, I will say that:
1) It is justified when you cannot accurately determine the data structure in advance, or the structure will change frequently;
2) It does if your data fits well into a document tree storage system.
3) I have not come across two SQL and NoSQL systems at the same time. But that doesn't mean it's impossible. It will just be hard for you to think in two different directions at once.

Answer 5

Use MongoDB. Much easier and faster than SQL.