It actually works pretty nicely. Most of our apps are small and focused, and we nest apps within each other heavily. It's fairly common for example to see an a

It actually works pretty nicely. Most of our apps are small and focused, and we nest apps within each other heavily. It's fairly common for example to see an app introduce some models, Python APIs to work with them, and business logic, and then to have a sub-app for the web API and bits relating to that, and a sub-app for the admin interfaces (we don't use the Django admin). Example: - orders - refunds - shipping - royal_mail - click_and_collect - fraud - fraud_blacklists - returns This means that working on our Click and Collect integration, one only needs to hold in their head the current app, and maybe some APIs provided by the apps above it. It's relatively uncommon to import across apps on different branches of the tree, and when we do that's typically only to top-level apps containing the most core models, or for very explicit public APIs provided to the whole site (which might be re-exported from an __init__.py up the tree anyway). I find it a pretty nice codebase to work on. We're hiring too https://www.thread.com/jobs/software-engineer https://www.thread.com/jobs/software-engineer