K
K
Kroid2016-10-26 13:09:19
NoSQL
Kroid, 2016-10-26 13:09:19

Which document database to choose?

What database would you recommend so that:
0) It is stable, it will not fall from the bullshit on the production
1) It was possible to store json in it and flexibly filter by the content of this json when searching
2) It is more or less fast
3) It has a normally implemented replication master-slave
4) It was possible to make indexes on certain fields
First of all, mongodb comes to mind, but I heard bad reviews from friends: "mongo is either slow or dead."

Answer the question

In order to leave comments, you need to log in

3 answer(s)
E
Eugene, 2016-10-26
@Nc_Soft

postgresql

A
Alexey Cheremisin, 2016-10-26
@leahch

See what to eat with. You can also use elasticsearch as nosql storage, as I do. We, I hope, are choosing not just an abstract horse in a vacuum, but something that will help us solve the problem.
Here with the description of the task in a question I also would begin.
As an example:
- you need to search a lot according to different criteria, the type of goods in the store, preferably with a language search, the documents are small and not branched - elasticsearch
- you need to search for unclear things in branchy documents, language and full-text search is not very necessary, but you need to calculate fields in depending on the search - mongodb, as an example, a database of train schedules and their movements in directions.
- you need to look for related information such as connections between people, such as seven handshakes - node4j for example.
And so on, for each plug there is a tricky corkscrew.

L
lega, 2016-10-26
@lega

If transactions are not needed, then Monga is the most. Everything is fine with speed. For 6 years I have never fallen from the bulldozer.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question