M
M
mr_drinkens2017-08-03 10:24:37
Django
mr_drinkens, 2017-08-03 10:24:37

Should I use Mongo with Django+Postgre?

Hello.
At the moment there is a project a la Trello (boards, lists, cards).
I thought about using Mongo in conjunction with Django + PostgreSQL. In postgri - to store basic (general) information (users, registration / authorization), and in mongo - the project itself (boards / lists / tasks).
Should I use this scheme? or stay entirely on PostgreSQL?
Guess who has done this kind of work.
Thank you in advance.

Answer the question

In order to leave comments, you need to log in

2 answer(s)
R
RidgeA, 2017-08-03
@RidgeA

The idea is so-so.
It is necessary to weigh all + and -
The boldest and most significant "-" is that either you will have to duplicate the data in order to be able to work with all possible (including those that will appear later) requirements for requesting data from the database, and here the complexity of synchronization and the risk of desynchronization. Or do joins in the code, which is still a crutch.

A
Alexey Ovdienko, 2017-08-03
@doubledare

Well, the option that NoSql is more useful in Trello-like projects is no doubt.
Have you thought about porting everything to monga? Well, like, you won’t be able to use ORM from django anymore) But the gain is that you don’t need to do nested queries. Mongo allows you to store nested documents and structures.
In terms of reliability, monga is the same good guy with scalability, like postgre. It’s just a dilemma here: either it’s steamed with several requests in postgre, or it’s steamed with migration to mongo and make requests already there.
Plus, Dzhanga has an ORM, and officially there is an ORM only for sql databases

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question