For a restaurant directory website, which database should I choose?

M

Maxim2020-09-02 19:09:09

NoSQL

Maxim, 2020-09-02 19:09:09

Greetings! Tell me, if I want to make a site with cards of establishments (restaurants), which will have standard attributes (I think you can imagine what: name, address, phone number, etc.), and then you can search the entire database of establishments with various filters (that is, it will be necessary to make selections from the database) then which database is optimal to choose? For example NoSQL for such data can be chosen?
I just honestly do not understand what is meant when MYSQL is recommended arguing the choice of topics "if you need data integrity and integrity". And what, in MongoDB or Cassandra, this safety can be broken?

Reply

Answer the question

In order to leave comments, you need to log in

3 answer(s)

S

Saboteur, 2020-09-02
@max_shane

Mongo is usually taken when the attributes are not very standard, or you need object-oriented storage.
If you don't know which database to choose, take regular SQL. You will choose another when you understand why exactly you need it.

V

Vladimir Korotenko, 2020-09-02
@firedragon

No difference. It all depends on the structure of the database.
For example, you have tables
tags
places
tag_places
You find in the filters what you need by tags, and select what you need by places. By the way, much faster.
And garbage in the form of json can also be stored in a relational database. Some even allow requests to be made

D

dmshar, 2020-09-02
@dmshar

The question sounds kind of weird. And why should you choose "MongoDB or Cassandra" if a task similar to yours was solved 100500 thousand times and mainly in SQL, which, moreover, were invented for such tasks (search in a well-structured array of information)?
Give at least one example when even MySQL is not enough for your task?