undefined | Better HN

0 pointsipaddr11mo ago0 comments

It easy but having separate app spaces by default instead of just one like Laravel makes it slightly harder for just a website case.

0 comments

imjonse11mo ago

You can use a single app, and it is probably the best way to go for the majority of projects - definitely the case for simple ones.

the__alchemist11mo ago

Concur. The multiple app paradigm doesn't fit any site I've built in Django. I make one called main.

hellojesus11mo ago

Idk if it's best practice, but I usually like to make apps similar to components, where I have an app for accounts which handles user accounts, and a files app which handles all the dimension and fact tables around user uploads, and a social app for social features, etc.

It makes it easy to compartmentalize the business logic in terms of module imports.

globular-toast11mo ago

This sounds similar to a modular monolith design. But you have to be careful not to directly import things between apps and especially not to make foreign keys between the models of different apps. We ended up doing that and just wishing it was one big app.

Modular monolith is a good idea and if you want to do it in Django then make small apps that just expose services to each other (ie. high-level business functions). Then have a completely separate app just for the UI that uses those services.

1 more reply

j / k navigate · click thread line to collapse