[sweave]

We love Python for multiple reasons but one of the reasons we chose to stick with the language is fastapi & its ecosystem, it's really a joy to work with.

When I started the project I chose MongoDB for simplicity but a PostgreSQL rewrite is on the roadmap ;)

[digi59404]

Are you planning on moving to Postgres from Mongo because you and the team have experienced pain with Mongo? Or is it because of Postgres’s popularity?

I’m not judging or anything; I’m just curious the decision making process for the switchover.

[jasfi]

OK, I was just wondering.

It sounds like you're not using an ORM if a rewrite is required?

[kdmccormick]

I work on a certain other open source LMS that stores some of its data in Mongo but has been gradually moving it all into a relational db.

It is true that the (home-baked) ORM we use on top of Mongo provides an abstraction layer which makes parts of the migration easier, but truly finishing the migration has and will feel like a long, gradual rewrite.

That's because Mongo and its "no-SQL" patterns permeated our original architecture. JSON everywhere, layers of caches to handle the inefficiency of complex Mongo queries, stringly-typed fail-quietly semantics, all that sort of fast-and-loose stuff. Truly moving to relational data (Django models, in our case) means replacing all those old patterns with, you know, thoughtfully designed data models and efficient SQL queries. Otherwise, the LMS would just be a Mongo app awkwardly grafted onto a SQL database.

[sweave]

Yes we'll use an ORM in the future so users can use their preferred database (sqlite for example), SQL Model by tiangolo & SQL Alchemy are great candidates!

[xenophonf]

I adopted SQLAlchemy ORM, Marshmallow-SQLAlchemy, and Alembic for a personal project and couldn't be happier with the results:

https://github.com/irtnog/lethbridge