B
B
bernex2016-04-09 08:19:19
MySQL
bernex, 2016-04-09 08:19:19

How to understand that it is worth using MongoDB?

Habit and experience do not let go of familiar databases. Opportunities for growth and future analytics and simplicity.
Of course mongo is not complicated and convenient. But how to understand, here it is necessary to use it? And not 10 tables in another database?

Answer the question

In order to leave comments, you need to log in

3 answer(s)
A
Alexander Prozorov, 2016-04-09
@bernex

Use Postgre and get in one bottle both a relational database and storage of denormalized data without a schema in JSONB fields with the possibility of indexing them.

A
Alexey Ukolov, 2016-04-09
@alexey-m-ukolov

How to understand that it is worth using MongoDB?
The algorithm is very simple:
An attentive reader may notice that if in this algorithm we replace Mongo with %any tool% , and relational databases with %any other tool% , then this algorithm becomes the Universal Tool Selection Algorithm. An even more attentive reader may notice that UAVI is applicable to absolutely any human activity.
PS Yesterday at DUMP, Oleg Bunin said that he had not seen a single task where it was necessary to use a NoSQL database. Some people applauded him wildly.

S
Silm, 2016-04-09
@Silm

If you need to store relational data, then use relational DBMS.
If your data is hierarchical structures, documents, then use document-oriented DBMS.
When in doubt about a responsible project, a more familiar tool should be preferred. When in doubt about a fan project - less familiar.
You can use 2 subd at once in one project.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question