> On Mar 26, 2023, at 6:47 PM, Damanjeet Singh <mailtoda...@gmail.com> wrote: > > Depending on the requirements. Either two different databases or point to one > database. > > Or > Link one database to master (read and write) > > Another database instance to read only. > > And you can change Another database to main. >
Thanks for your patience in answering my doubts. But I still have some follow up questions. If it is the same database, and the migration changes the schema, won’t the older application code instances have the same problem with backward incompatible schema changes? And if it is two databases, how does it work? If you set the older database to read-only, then traffic on the write path of the older application will break. If you somehow connect the two in sync, won’t the DDL changes on the primary replicate to the other replica as well, again causing the older application to break? - Sandip > > > On Sun, 26 Mar 2023, 22:33 Sandip Bhattacharya, <sand...@showmethesource.org > <mailto:sand...@showmethesource.org>> wrote: >> >> >>> On Mar 26, 2023, at 4:32 PM, Damanjeet Singh <mailtoda...@gmail.com >>> <mailto:mailtoda...@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. >> >> >> >> Do you do blue-green deployments with two different databases? >> >> - 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CF4FC246-87DD-4F31-A7E7-D3B9682F7FC0%40showmethesource.org.
