Production routing architecture — Katta loyihada route'larni tashkil qilish
Enterprise darajadagi TanStack Router arxitekturasi: Feature-based papkalar tuzilmasi, 'Thin Route Files' prinsipi, jamoaviy miqyoslanish va eng yaxshi amaliyotlar.
66-dars
Production routing architecture — Katta loyihada route'larni tashkil qilish
Kichik o‘quv loyihalarida barcha kodlarni — API so‘rovlari, murakkab JSX shakllari, holatlar va dizaynni to‘g‘ridan-to‘g‘ri src/routes/ ichidagi fayllarga yozish odatiy hol.
Ammo yirik (Enterprise) hajmdagi loyihalarda o‘nlab dasturchilar bir vaqtda ishlaganda, marshrut fayllari 500–1000 qatorli chalkash "lag‘mon kod"ga (Spaghetti Code) aylanadi. Bitta sahifani o‘zgartirish butun tizim bo‘ylab ziddiyatlar (Git merge conflicts) va xatoliklarni keltirib chiqaradi.
Ushbu darsda yirik xalqaro kompaniyalar foydalanadigan Feature-Based (Modulli) arxitektura va "Thin Route Files" (Yupqa Route Fayllari) tamoyilini ko‘rib chiqamiz.
1. Hayotiy o‘xshatish: Xalqaro aeroport va Avia-zavod
Tasavvur qiling, siz katta xalqaro aeroportdasiz:
- Aeroport terminallari va yo‘l ko‘rsatkichlari (
src/routes/— Yupqa qatlam): Yo‘lovchiga qaysi darvozaga (Gate) borishni ko‘rsatadi (/posts/$postId), pasport va vizani tekshiradi (beforeLoad/validateSearch). Terminallarning vazifasi faqat yo‘naltirishdir — u yerda samolyot yig‘ilmaydi yoki taom pishirilmaydi. - Maxsus sexlar va xizmat ko‘rsatish departamentlari (
src/features/— Biznes mantiq): Samolyotga yonilg‘i quyish, yo‘lovchilar taomini tayyorlash, yuklarni saralash markazi kabi og‘ir ishlar alohida mustaqil binolarda bajariladi. - Agar aeroport zali ichida samolyot ta'mirlansa, aeroportda xaos yuz bergan bo‘lardi!
2. Enterprise Papkalar Strukturasi
Katta loyihalarda eng maqbul va sinalgan katalog tuzilmasi:
src/
├── app/ # Global sozlamalar (router.tsx, queryClient.ts, providers)
├── features/ # Mustaqil Biznes Modullar (Domain Modules)
│ ├── auth/
│ │ ├── api/ # authApi.ts
│ │ ├── components/ # LoginForm.tsx, RegisterForm.tsx
│ │ ├── queries/ # authQueries.ts, authMutations.ts
│ │ └── types.ts # User, Role, Session turlari
│ ├── posts/
│ │ ├── api/ # postsApi.ts (fetchPosts, updatePost)
│ │ ├── components/ # PostCard.tsx, PostDetailView.tsx, PostEditor.tsx
│ │ ├── queries/ # postQueries.ts (queryOptions)
│ │ └── types.ts # Post, Comment turlari
│ └── users/
│ ├── api/
│ ├── components/ # UserProfileView.tsx, UserAvatar.tsx
│ └── queries/
│
└── routes/ # Faqat TanStack Router yo'l xaritasi (Yupqa qatlam)
├── __root.tsx # Global Layout va Context
├── index.tsx # / (Bosh sahifa)
├── posts/
│ ├── index.tsx # /posts ro'yxati entry-point
│ └── $postId.tsx # /posts/$postId tafsiloti entry-point
└── auth/
├── login.tsx # /login entry-point
└── register.tsx # /register entry-point
3. "Thin Route Files" Prinsipi
Ushbu arxitekturada src/routes/ papkasidagi fayllar faqatgina marshrut qobig‘i (glue code) vazifasini bajaradi:
- URL parametrlarini tekshiradi (
params,validateSearch). - Ruxsatlarni nazorat qiladi (
beforeLoad). - Kerakli feature query'sini chaqiradi (
loader). - Tayyor vizual feature komponentini ekranga chiqaradi (
component).
1-bosqich: Biznes mantiqni Feature ichida yozish
// src/features/posts/queries/postQueries.ts
import { queryOptions } from '@tanstack/react-query'
export const postDetailQueryOptions = (postId: string) =>
queryOptions({
queryKey: ['posts', postId],
queryFn: async () => {
const res = await fetch(`https://api.example.com/posts/${postId}`)
if (!res.ok) throw new Error('Post topilmadi')
return res.json()
},
staleTime: 1000 * 60 * 5,
})
// src/features/posts/components/PostDetailView.tsx
import type { Post } from '../types'
interface Props {
post: Post
}
// Barcha og'ir UI, animatsiyalar va tugmalar shu yerda yashaydi
export function PostDetailView({ post }: Props) {
return (
<article className="post-detail-view">
<header>
<h1>{post.title}</h1>
<span className="author">Muallif: {post.author}</span>
</header>
<div className="body">{post.body}</div>
</article>
)
}
2-bosqich: Yupqa Route fayli (src/routes/posts/$postId.tsx)
Endi router fayliga qarang — u qanchalik toza, ixcham va o‘qishga oson:
// src/routes/posts/$postId.tsx
import { createFileRoute } from '@tanstack/react-router'
import { postDetailQueryOptions } from '@/features/posts/queries/postQueries'
import { PostDetailView } from '@/features/posts/components/PostDetailView'
export const Route = createFileRoute('/posts/$postId')({
// 1. Loader feature query options'ni ishlatadi
loader: async ({ context, params }) => {
return context.queryClient.ensureQueryData(
postDetailQueryOptions(params.postId)
)
},
// 2. Komponent feature ichidagi tayyor view'ni render qiladi
component: PostRouteWrapper,
})
function PostRouteWrapper() {
const post = Route.useLoaderData()
return <PostDetailView post={post} />
}
[!TIP] Agar sahifani Lazy Loading qilish kerak bo‘lsa,
PostRouteWrapperni shunchakisrc/routes/posts/$postId.lazy.tsxfayliga ko‘chirib qo‘yish kifoya!
4. Arxitekturaviy Bog‘liqlik Qoidasi (Mermaid Diagram)
Katta loyihalarda arxitektura buzilmasligi uchun qat'iy yo‘nalish qoidasi (Import Boundary) amal qiladi:
flowchart TD
Routes["src/routes/ (Yupqa Marshrut Qatlami)"] -->|"Import qilishi mumkin"| Features["src/features/ (Biznes Modullar)"]
Features --> API["api/"]
Features --> Components["components/"]
Features --> Queries["queries/"]
Features --> Types["types.ts"]
Features -.->|"QAT'IYAN TAQIQLANADI ❌"| Routes
style Routes fill:#f9f,stroke:#333,stroke-width:2px
style Features fill:#bbf,stroke:#333,stroke-width:2px
Qat'iy qoida: routes doimo featuresdan import qiladi, lekin features ichidagi birorta komponent yoki funksiya hech qachon routesdan import qilmasligi shart! Bu modullarning to‘liq mustaqil (decoupled) bo‘lishini ta'minlaydi.
5. Monolit Marshrutlar va Feature-Based Arxitektura taqqosi
| Mezon | Monolit (Barcha kod routeda) | Feature-Based + Thin Routes |
|---|---|---|
| Route fayli hajmi | 400–800 qator (oqishi qiyin) | 20–40 qator (o‘ta ixcham va toza) |
| Jamoaviy miqyoslanish | Doimiy Git konfliktlari | Har bir dasturchi o‘z feature'ida erkin ishlaydi |
| Modullarni qayta ishlatish | Deyarli imkonsiz | Istalgan feature'ni boshqa loyihaga ko‘chirsa bo‘ladi |
| Testlash qulayligi | Routing bo‘lmasa komponentni testlab bo‘lmaydi | Feature komponentlarini mustaqil unit-test qilish mumkin |
| Fayllar topilishi | Butun ilova aralash-qurash | Har bir soha o‘z papkasida jamlangan |
Xulosa
- Katta loyihalarda routing fayllarini biznes mantig‘i bilan to‘ldirmaslik (Thin Route Files) asosiy qoidadir.
- Feature-Based papkalar tuzilmasi loyihani modullarga (
auth,posts,users) ajratib, jamoaviy ishlash samaradorligini keskin oshiradi. src/routes/papkasi faqatgina URL strukturasini ko‘rsatuvchi,beforeLoad,validateSearchvaloaderni feature'lar bilan bog‘lovchi yengil ko‘prik bo‘lib xizmat qiladi.- Bu arxitektura loyihani yillar davomida barqaror, toza va oson kengaytiriladigan darajada saqlaydi.