Architecture

Цей документ містить наскрізні карти, які зв'язують теорію з фінальним кодом.

HTTP request lifecycle

flowchart TD
    Browser["Browser"] --> DNS["DNS"]
    DNS --> TCP["TCP/TLS"]
    TCP --> Server["Development server або reverse proxy"]
    Server --> Middleware["Django middleware"]
    Middleware --> URLDispatcher["URL dispatcher"]
    URLDispatcher --> View["View"]
    View --> Form["Form validation"]
    View --> Selector["Selector"]
    View --> Service["Service"]
    Selector --> ORM["ORM"]
    Service --> ORM
    ORM --> DB["SQLite або PostgreSQL"]
    View --> Template["Template"]
    Template --> Response["HTML response"]
    Response --> Browser

Django MVT

flowchart LR
    URL["URL pattern"] --> View["View"]
    View --> Model["Model/ORM"]
    View --> Template["Template"]
    Template --> Browser["Browser"]

CRUD flow

sequenceDiagram
    participant B as Browser
    participant V as View
    participant F as Form
    participant S as Service
    participant D as Database
    B->>V: GET form
    V-->>B: render form
    B->>V: POST data
    V->>F: validate
    F-->>V: cleaned_data
    V->>S: create/update/delete
    S->>D: transaction
    V-->>B: redirect

Authentication flow

sequenceDiagram
    participant B as Browser
    participant A as Auth view
    participant S as Session store
    participant M as AuthenticationMiddleware
    B->>A: username/password
    A->>S: create session
    A-->>B: Set-Cookie sessionid
    B->>M: next request with cookie
    M->>S: load session
    M-->>B: request.user available to view

Object permission flow

flowchart TD
    PK["URL pk"] --> User["authenticated user"]
    User --> ScopedQS["scoped queryset"]
    ScopedQS --> Lookup["object lookup"]
    Lookup --> Allowed{"found?"}
    Allowed -->|yes| View["render or mutate"]
    Allowed -->|no| Deny["404 або PermissionDenied"]

Testing pyramid

flowchart TD
    E2E["E2E: Selenium"] --> Integration["Integration: Django TestClient"]
    Integration --> Unit["Unit: models, services, forms"]

Async і WebSocket flow

sequenceDiagram
    participant JS as Browser JavaScript
    participant ASGI as ASGI application
    participant PTR as ProtocolTypeRouter
    participant Auth as AuthMiddlewareStack
    participant Router as URLRouter
    participant C as Consumer
    participant L as Channel layer
    JS->>ASGI: WebSocket handshake
    ASGI->>PTR: protocol=websocket
    PTR->>Auth: load user from session
    Auth->>Router: route /ws/groups/pk/chat/
    Router->>C: GroupChatConsumer.connect
    C->>L: group_add
    JS->>C: send message
    C->>L: group_send
    L->>C: deliver event to consumers
    C->>JS: message frame

Production deployment

flowchart LR
    Internet["Internet"] --> DNS["DNS"]
    DNS --> HTTPS["HTTPS"]
    HTTPS --> Nginx["Nginx recommended"]
    Nginx --> App["Gunicorn/Uvicorn recommended"]
    App --> Django["Django"]
    Django --> Postgres["PostgreSQL"]
    Django --> Redis["Redis for Channels"]
    Nginx --> Static["Static files"]

Компоненти Nginx, Gunicorn/Uvicorn, PostgreSQL і Redis є рекомендованим production stack. Поточний Docker setup ще потребує виправлення перед використанням як готового deployment.