Django

How ArrayMatic uses Django

Django is our go-to Python framework when a project needs a structured, opinionated backend from day one. We reach for it when the application has significant data modelling complexity, requires a built-in admin interface for operations teams, or is built by a Python-first engineering team that benefits from strong conventions. The batteries-included approach — built-in ORM, migrations, authentication, permissions, and an extensible admin panel — means we spend time on the application, not the infrastructure.

Our Django projects follow a clean architecture: domain models in the ORM, business logic isolated in service classes rather than fat models, and API endpoints handled by Django REST Framework with OpenAPI documentation generated automatically. Background tasks run on Celery with Redis as the broker. Test coverage uses pytest-django from day one, integrated into the CI pipeline before the first feature ships.

When we choose Django over alternatives

For lightweight Python APIs without a database layer we use Flask. For high-concurrency async APIs where the event loop matters we use FastAPI. Django is the right choice when the project needs a relational database, complex permission logic, or a customisable admin interface for internal teams. We avoid Django for single-function microservices or event-driven pipelines where its request-response model is the wrong shape for the workload.

Typical project types

• SaaS platforms with multi-tenancy and role-based access control
• Internal operations and data management dashboards
• REST API backends consumed by React or React Native frontends
• Content management systems with custom editorial workflows