Apa iku arsitektur MVT?

Question

Accepted Answer

Django ngetutake arsitektur **MVT (Model-View-Template)** — variasi saka pola MVC klasik. Pisahe aplikasi dadi telung lapis: **Models** (data), **Views** (logika), lan **Templates** (presentasi). Paham karo lapisan-lapisan iku yen arep ngerti endi-endi kode kudu diselehake. ## Telung lapis ```text Model → the DATA layer: defines structure & talks to the database (the ORM) View → the LOGIC layer: processes requests, fetches data, returns responses Template → the PRESENTATION layer: HTML with placeholders for dynamic data ``` ## Carane gumana bebarengan (alur request) ```text Request → URLconf (routing) → VIEW → queries MODELS → renders TEMPLATE → Response ``` ```python # MODEL — defines the data (models.py) class Article(models.Model): title = models.CharField(max_length=200) body = models.TextField() # VIEW — the logic: fetch data, pass to a template (views.py) def article_list(request): articles = Article.objects.all() # query the MODEL return render(request, "articles.html", {"articles": articles}) # render a TEMPLATE ``` ```html {% for article in articles %}

{% endfor %} ``` View nggabungake kabeh: nampa request, takon models kanggo data, lan render template karo data iku kanggo ngasilake response. ## MVT vs MVC ```text Classic MVC: Model — View — Controller Django MVT: Model — Template — View The mapping (a common point of confusion): Django's VIEW ≈ MVC's CONTROLLER (the logic that handles requests) Django's TEMPLATE ≈ MVC's VIEW (the presentation) Model is the same in both → Django says the framework itself acts as the "controller" (URL routing/dispatch). ``` Penanaan beda saka MVC: **View** Django maeng tindak minangka *Controller* MVC (logika nangani request), lan **Template** Django maeng tindak minangka *View* MVC (presentasi). Routing framework nangani dispatch. ## Apa apa penting saka pemisahan iki ```text ✓ Separation of concerns — data, logic, and presentation are independent ✓ Maintainability — change the template without touching logic, etc. ✓ Reusability & testability — test views independently, reuse models/templates ``` ## Apa iku penting Arsitektur MVT iku pola struktural dasar saka saben aplikasi Django — ngerti iku ngomongake **endi-endi kode kudu diselehake** (definisi data ing models, logika nangani request ing views, presentasi HTML ing templates), sing kudu banget kanggo atur proyek Django kanthi bener. Pemisahan kapentingan sing ditakse iku gawe aplikasi bisa diomah (ganti presentasi tanpa jabang logika), bisa diuji (uji views lan models kanthi misah-misah), lan bisa dibalakake. Samene pentinge ngerti **pemetaan MVT-vs-MVC** — sumber kebingungan sing asring muncul — ngendi "View" Django sejatine tindak minangka padha controller (logika) lan "Template" Django padha view (presentasi); ngerti iki yen ngersake jenenge lan tulung developer saka framework MVC. Alur request (URL routing → view → models → template → response) iku model pikiran carane saben request Django diolah, gawe MVT dadi ilmu dasar sing kudu tahu, sing dadi landasan cara kowe atur lan pikir babagan kabeh kode Django.