architecting-django

Structure a Django app with hexagonal architecture by isolating external boundaries with adapters, separating queries from commands at the service layer, and using settings-driven dependency injection to load modules. This enforces Active Record style modeling while keeping core logic testable.

The best way to isolate external dependencies in Django is by using hexagonal adapters. They decouple external systems from your core logic, allowing you to inject mock adapters via settings during testing to ensure clean separation of concerns.

Yes, you can apply hexagonal architecture and dependency injection to NetBox plugin development. The same Active Record-inspired models, service layers, and settings-driven adapter loading ensure scalable architecture and clean testability across plugin modules.

Settings-driven dependency injection for Django adapters works by loading adapter implementations dynamically from project settings. This mechanism allows you to swap external system integrations or mock services without modifying the core service layer logic.

You should separate queries from commands in a Django service layer whenever you need clean architecture and strict separation of concerns. This Active Record-inspired boundary keeps read operations distinct from state-changing commands, simplifying adapter integration and testing.

Use hexagonal adapters instead of standard Django models to prevent external integrations from corrupting your domain logic. Adapters provide a clear boundary for external systems, enabling settings-driven dependency injection and making your service layer fully testable.