New to django, so wanted to ask some questions that I didn’t find good resources for:
1. If you deploy django apps using docker, do you run migrations before launching gunicorn/uwsgi etc within the docker image?
2. If you do, how does rolling migrations work? Won’t the non-upgraded replicas start erroring if the new schema is not backward compatible?
3. How do you do non-backward compatible schema upgrades? Do you do it out of band from deployments? Do you shift traffic to a different cluster, and then zero traffic upgrade the whole cluster at once?
Thanks,
Sandip
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/A9719D24-F6DA-45A6-A30A-EA8EA34754A1%40showmethesource.org.
On Mar 26, 2023, at 4:32 PM, Damanjeet Singh <mailt...@gmail.com> wrote:3. How do you do non-backward compatible schema upgrades? Do you do it out of band from deployments? Do you shift traffic to a different cluster, and then zero traffic upgrade the whole cluster at once?Daman: Blue Green deployment can help. You can distribute traffic to old and new. When all stable then move everything. You can use kubernetes with helm.
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/66989169-7601-4CA1-A54B-B9B29F7B719B%40showmethesource.org.
On Mar 26, 2023, at 6:47 PM, Damanjeet Singh <mailt...@gmail.com> wrote:Depending on the requirements. Either two different databases or point to one database.OrLink one database to master (read and write)Another database instance to read only.And you can change Another database to main.