Scaling Django for Multiple Teams
88 views
Skip to first unread message
bliy...@rentlytics.com
Apr 18, 2016, 8:11:38 PM4/18/16
to Django developers (Contributions to Django itself)
Hey,
I have two issues I'm looking at solving at work, and I'm looking for a couple suggestions as to how other people have solved this. The two things are:
* scale out their django installation to allow for smaller releases (I'm thinking microservices, but it could also be internal django apps or who knows what else)
* minimizing the impact of migrations during releases (aka we want to be able to release in the middle of the afternoon
Currently we put up a maintenance page whenever we are doing database operations (aka migrations). This seems like a recommended best practice.
One way I was thinking about addressing this issue was to break all of our models out into a separate repo. That way we'd only need to deploy migrations when the models themselves have deployed. For code that needs the models, we could pip install the repo as an app and away we go. Likewise it seems like I could break up different parts of our app via a similar strategy.
Does this seem viable? How have other people solved this kind of problem?
Thanks,
-Ben
I have two issues I'm looking at solving at work, and I'm looking for a couple suggestions as to how other people have solved this. The two things are:
* scale out their django installation to allow for smaller releases (I'm thinking microservices, but it could also be internal django apps or who knows what else)
* minimizing the impact of migrations during releases (aka we want to be able to release in the middle of the afternoon
Currently we put up a maintenance page whenever we are doing database operations (aka migrations). This seems like a recommended best practice.
One way I was thinking about addressing this issue was to break all of our models out into a separate repo. That way we'd only need to deploy migrations when the models themselves have deployed. For code that needs the models, we could pip install the repo as an app and away we go. Likewise it seems like I could break up different parts of our app via a similar strategy.
Does this seem viable? How have other people solved this kind of problem?
Thanks,
-Ben
Tim Graham
Apr 18, 2016, 8:31:34 PM4/18/16
to Django developers (Contributions to Django itself)
This mailing list is for the development of Django itself. Please use django-users for usage questions. Is there some place we could improve that would have helped you identify the correct list?
Ben Liyanage
Apr 18, 2016, 8:38:33 PM4/18/16
to django-d...@googlegroups.com
My bad--see you guys on the other side.
-Ben--
You received this message because you are subscribed to a topic in the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-developers/dTTtiSXgiz0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to django-develop...@googlegroups.com.
To post to this group, send email to django-d...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/80d98b66-4c80-4b45-af68-a24bbaa7a6bd%40googlegroups.com.
--
Ben Liyanage | Software Engineer | Rentlytics, Inc.
Reply all
Reply to author
Forward
0 new messages