Django is a good instrument (not the best, but good enough) to create web apps as fast as possible, it includes a lot of useful batteries which allow to start up production-ready MVP in a days. But if you are going to evolve your app you need to pay attention…

Hi there! This is the last post in a series explaining separation of existing Django project on several subapps: Migrate your Django monolith to microservices. The 1st step — preparation. Migrate your Django monolith to microservices. The 2nd step — understanding Django model and migration management. Migrate your Django monolith…

Hi there! Guess almost every developer had thought about dividing Django monolith on several smaller services, when you refactor, move code between applications in your project. Usually this thoughts end on Django’s models management, there is plenty of problems: how to move models without breaking migrations graph; how to hold…

Thanks for the article, but thereis one huge minus, especially if you have already have legacy code - you must call QuerySet's using() method everywhere you need non default limits. It may lead to rewriting a lot of code. If your project is running in different environments (e.g inside several docker containers) the better way I guess is to separate "running mode" by environmental variable (RUNNING_MODE for example) and set it for every source: RUNNING_MODE=app|celery|cron|... . And get limit time looking on this env variable.