K
K
krekerjun2017-10-22 15:20:49
Database
krekerjun, 2017-10-22 15:20:49

Which database to choose for your task?

Good day. What is the best database to choose?
My task has a lot of data related to each other, that is, for example, there are objects of the form:

{name: 'title one', child: 3}
{name: 'title two', childid: 1}

There is data in the child table, of the form:
{id: 3, task: 11, desc: 'desc1'}
{id: 3, task: 12, desc: 'desc2'}
{id: 1, task: 11, desc: 'desc3'}

There is data in the task table, of the form:
{id: 11, task: 'do smth'}
{id: 12, task: 'do smth2'}

At the output, I should get a relationship between the first, second and third table, for example:
{name: 'title one', task: 'do smth', desc: 'desc1'}
{name: 'title one', task: 'do smth2', desc: 'desc2'}
{name: 'title two', task: 'do smth', desc: 'desc3'}

As I understand it, NoSQL does not cope well with such tasks? How to approach reasonably to the choice of the Database? There is only experience with mysql, but maybe there are more reasonable options?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
K
kn0ckn0ck, 2017-10-22
@kn0ckn0ck

The choice of database is an architectural decision that will affect everything in your project. It is necessary to treat the choice responsibly, and not superficially - as it is now.
All data is always connected in some way, so this cannot be a criterion for choosing a technology for storing / retrieving them.
If you are making architectural decisions on a project, then consider many potential use cases for data, types of data, and so on. Just sit down and write down: a) you need this, b) you need that, c) and then another way, d) ...
Having compiled a table of use cases (requirements in fact), work out the strengths and weaknesses for each of the technologies that you think applicable here.
Form a systematic and balanced decision.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question