Post

Oh hi blue sky. Just popping in to say: Introducing Django RAPID architecture, the guidebook I've been writing (on and off) for a year or so, and thinking about for my entire career. www.django-rapid-architecture.org

It's a free, opinionated guide to structuring real‑world Django codebases so they stay understandable and malleable as they grow. It’s not a new framework, and it doesn’t try to hide Django. Instead, it leans into Django’s strengths and focuses on a few simple ideas:

- Keep models thin: data definitions, not “god objects”. - Organise code by responsibility (readers, actions, interfaces, data) rather than by app. - Put most business logic in plain functions, not in fat models or deep class hierarchies.

- Keep views thin: treat GET as "read some data" and POST as "do an action". - Design endpoints around real frontend use cases (Backend For Frontend) instead of idealised resources. - Control queries carefully to avoid performance traps.