Single App scalability Django -


i find common theme upon research of using apps in django "if want reuse function in project, create app it". not plan on creating other projects in future. however, plan on scaling project @ point (to multiple cities and/or regions).

i have come own conclusion not bouncing folder folder multiple apps in project , freedom of naming things in way comprehensive me (do not plan on using other peoples sources - understand requires more time , effort on part). find easier @ things in 1 place, leaves me large amount of code in single app.

  1. is there significant performance advantages/disadvantages using single app?

  2. in terms of scaling data storing in future (if lucky enough have problem), using single app cause complexity of send data?

  3. would using single app harder test doing multiple apps?

every framework built purpose , important understand psychology behind it. django is built based on app mentality, divides project multiple apps. built on unix philosophy of “do 1 thing , well.”

1)there no significant performance issues when maintain single app.

2)yes, app scales gradually face issues in maintaining code bases. since there no such demarcation responsibilities understanding code , further development becomes tedious job.

3)dividing project apps gives fair idea of has tested. hence single app mentality affects te sting too....


Comments

Popular posts from this blog

inversion of control - Autofac named registration constructor injection -

verilog - Systemverilog dynamic casting issues -

ios - Change Storyboard View using Seague -