Django and mongodb about realworld

[jamesbrewerdev]

Not sure. Django'S ORM sits between the database and the logic, so decoupling isn't an issue. That said, Django's ORM doesn't provide native support for Mongo. There are packages available that do, but I'm not sure how good they are. I'd have to do more research to say how much work it would be.

…

On Tue, Apr 25, 2017 at 8:32 AM Eric Simons ***@***.***> wrote: @BRWR <https://github.com/brwr> how hard do you think it would be for someone to fork your Django codebase and have it use mongo instead? i.e. how decoupled is the DB from logic? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#52 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AD5-rMZ2FzOmfbWOjWg2uXpleqPY7WVCks5rzhH6gaJpZM4NHYSZ> .

[EricSimons]

@BRWR how hard do you think it would be for someone to fork your Django codebase and have it use mongo instead? i.e. how decoupled is the DB from logic?

[jamesbrewerdev]

Update: After looking into this more, I think it's a decent amount of work. It might be less for something more familiar with building MongoDB data models.

Basically, relational and non-relational data need to be modeled differently. And while the logic isn't tied to what's in the database, it is (necessarily) tightly coupled to the Django model implementation. If the model changes, then some of the logic will change too. Making the code work with Mongo would require model changes.

[geromegrignon]

Closing the issue as there is no recent activity.