Hi José, thanks for joining the discussion! The sibling to this post (by “traverseda”) is more informed and informative than I could hope to write. I will add

Hi José, thanks for joining the discussion! The sibling to this post (by “traverseda”) is more informed and informative than I could hope to write. I will add that Django has Manager classes that have default behavior included for interacting with the query API, and they can be customized to your needs. You can even have multiple managers for a given model. https://docs.djangoproject.com/en/4.1/topics/db/managers/ https://docs.djangoproject.com/en/4.1/topics/db/managers/ It’s been a few years since I used Django, but I remember its model layer fondly, and still follow the framework’s release processes. One of the areas where Django lags is being fully async (Python imposed a lot of limitations on async operations for most of its life). The upcoming 4.2 release of Django is laying the groundwork for async DB operations.