Built a Project using Djongo, there are a lot of dependency conflicts, is this feasible long term?

[dense badge]

Hi, I've spent the last couple of days working on an ios project using djongo as my backend server. I'm still in the beginning stages essentially but the more complex the project gets it seems like there are a lot of dependency conflicts because of Djongo. It seemed like Djongo would be the easiest to work with as a beginner but now I'm starting to rethink. I just read that djongo is not maintained so now I'm thinking about switching but I'm not sure to what. I'm mainly worried about scalability.

TL;DR

Built an app with Djongo but there are a lot of conflicts and have read others warning to stay away from djongo. Should I jump ship before I get too deep? And if I do, what should I switch to? Pymongo? MongoEngine?

[spiral bane]

@dense badge did you know Mongodb officially released a Django backend? https://www.mongodb.com/docs/languages/python/django-mongodb/current/

Apart from that, is there a reason you're going for mongodb as opposed to a relational database?

[dense badge]

My partner and I decided with mongodb mainly because I used it a few times in the past and I found that their interface was pleasant to use. I also only really know python and read that mongo was a popular choice as a db

Thank you for the link! I'll look into it

[spiral bane]

I would truly advise you go for an RDBMS. Most frameworks use those as the primary persistence storage of choice and they are widely used and supported. Not to mention the documentation and community support out-there (or in here even) is just more readily accessible and available.

Also, apart from "Graph" domains, you will be able to properly represent and use your domain models with ease.

So, one last warning 😆 - please use Postgres! 💚

[dense badge]

Thanks for the advice! Ill bring this up with my partner!