2-ma’ruza matni · Korxona ilovalarini dasturlash
Qatlamli arxitektura · MVC va Laravel · Repository va Service Layer · DTO va Unit of Work · Loyiha strukturasi
Buyurtma yaratish kodi 300 qatorlik controller metodida yozilgan. Ertaga xuddi shu buyurtmani API va Excel importi orqali ham yaratish kerak. Nima qilasiz? Kodni nusxalash yagona yo‘lmi? Avval o‘ylab ko‘ring, keyin muhokama qilamiz.
Biznes-jarayon (buyurtma yaratish, rezerv, QQS) HTTP dan ajratilib, alohida servis klassiga (Service Layer) chiqariladi. Controller, API va import shu servisni chaqiradi; ma’lumot kirishi esa model yoki repository da. Shunda qoida bir joyda o‘zgaradi va servisni bazasiz, soxta repository bilan testlash mumkin.
DB::transaction yondashuviniVazifalarni ajratish · to‘rt qatlam · bog‘liqlik yo‘nalishi · semiz controller
Qatlamli arxitektura (layered architecture) — ilovani vazifasi bo‘yicha gorizontal qatlamlarga bo‘lish usuli. Har bir qatlam bitta turdagi masalani hal qiladi va faqat o‘zidan pastdagi qatlam xizmatlaridan foydalanadi. Asosiy tamoyil — vazifalarni ajratish (separation of concerns): HTTP so‘rovni o‘qish, biznes-qoidani tekshirish va ma’lumotni saqlash — uch xil masala, ular uch xil sababga ko‘ra o‘zgaradi. Bitta joyga aralashtirilsa, bir sababli o‘zgarish boshqalarini buzadi.
Korxona ilovalarida odatda to‘rt qatlam ajratiladi. Taqdimot qatlami (presentation): controller, forma so‘rovlari (Form Request), Blade ko‘rinishlari, Livewire komponentlari, API Resource lar — kirish ma’lumotini qabul qiladi va javobni shakllantiradi. Ilova (servis) qatlami: OrderService, StockService — biznes-jarayonni boshqaradi, tranzaksiya chegarasini belgilaydi. Domen qatlami: modellar, enumlar (OrderStatus), qiymat obyektlari, domen istisnolari (InsufficientStockException) — sohaning tushunchalari va qoidalari. Ma’lumotlarga kirish va infratuzilma qatlami: Eloquent so‘rovlari, repository lar, tashqi API klientlari, fayl tizimi, navbatlar.
Bog‘liqlik yo‘nalishi faqat yuqoridan pastga: controller servisni chaqiradi, servis repository yoki modelni chaqiradi, lekin hech qachon aksincha emas. Model ichida request() yoki session() chaqirish, servis ichida redirect() qaytarish — qatlam chegarasini buzish. Qat’iy (strict) qatlamlashda har bir qatlam faqat bevosita pastdagi qatlamni chaqiradi; erkin (relaxed) qatlamlashda pastdagi istalgan qatlamni. Laravel da amaliy murosa: oddiy o‘qish ekranlarida controller modelga to‘g‘ridan-to‘g‘ri murojaat qilishi mumkin, lekin ma’lumotni o‘zgartiradigan har bir biznes-amal servis orqali o‘tadi.
Eng keng tarqalgan anti-namuna — semiz controller (fat controller): validatsiya, narx hisoblash, qoldiq tekshiruvi, bazaga yozish va e-mail yuborish bitta metodda. Uni qayta ishlatib bo‘lmaydi (API va import uchun nusxalanadi), testlash qiyin (HTTP so‘rov va baza kerak), o‘qish og‘ir. Qatlamlarga ajratishning narxi ham bor: ko‘proq fayllar va sinflar. Shuning uchun qatlamlar soni masala murakkabligiga mos bo‘lishi kerak — oddiy ma’lumotnoma CRUD i uchun servis va repository yozish shart emas, buyurtma va ombor oqimi uchun esa albatta kerak.
OrderService, StockService — jarayon, tranzaksiya chegarasiOrderStatus enumi, qiymat obyektlari, domen istisnolariProductRepository, tashqi API, navbatlar, fayllarStoreOrderRequest daOrderService::create() dafunction topish(string $sku): ?array // ma’lumot qatlami { return ['UN-001' => ['price' => 15000]][$sku] ?? null; } function narxla(string $sku, int $qty): int // biznes qatlami { $p = topish($sku) ?? throw new DomainException("$sku topilmadi"); return $p['price'] * $qty; } // taqdimot qatlami: kirish → javob (HTTP kodi) foreach ([['UN-001', '3'], ['XX-999', '1']] as [$sku, $qty]) { try { $jami = narxla($sku, (int) $qty); echo "200 $jami\n"; } catch (DomainException $e) { echo "422 ", $e->getMessage(), "\n"; } }
200 45000 422 XX-999 topilmadi
topish() — qayerdan o‘qishni faqat shu funksiya biladi (massiv, PostgreSQL, API)narxla() — qoida: mahsulot topilmasa — domen istisnosi(int) $qty — satrni turga keltirish — taqdimot qatlamining ishi200 / 422 — istisnoni HTTP javobiga aylantirish ham taqdimotdaHar bir holat uchun to‘g‘ri qatlamni tanlang.
InsufficientStockException tashlash.✓ Servis / domen — Bu biznes-qoida — servis yoki domen qatlamida, har qanday kirish yo‘li uchun bir xil.
counterparty_id maydoni majburiy va counterparties jadvalida mavjud ekanini tekshirish.✓ Form Request (taqdimot) — Kirish ma’lumoti formati va mavjudligi — StoreOrderRequest qoidalari.
✓ Repository (ma’lumot qatlami) — Murakkab o‘qish so‘rovlari ma’lumot qatlamiga — ProductRepository::lowStock().
Faqat yuqoridan pastga: taqdimot → servis → domen → ma’lumot; pastki qatlam yuqoridagini bilmaydi.
Kod qayta ishlatilmaydi (nusxalanadi), testlash qiyin, tranzaksiya chegarasi va mas’uliyat noaniq.
Oddiy ma’lumotnoma CRUD ida (masalan, kategoriyalar), biznes-qoida va bir nechta jadvalni o‘zgartirish bo‘lmaganda.
Model · View · Controller · index.php dan javobgacha · middleware
MVC (Model–View–Controller) — taqdimot qatlamini tashkil qilish namunasi. Model — ma’lumot va unga oid xatti-harakat (Laravel da Eloquent modeli: Order, Product); View — foydalanuvchiga ko‘rsatiladigan natija (Blade shabloni yoki JSON); Controller — so‘rovni qabul qilib, kerakli modelni yoki servisni chaqiradi va View ni tanlaydi. Muhim: MVC butun ilova arxitekturasi emas, u faqat taqdimot va ma’lumot o‘rtasidagi bog‘lanishni tartiblaydi. Biznes-jarayonlar “M” ichiga ham, “C” ichiga ham tiqilmasligi uchun servis qatlami qo‘shiladi.
Laravel da so‘rov hayot sikli quyidagicha. Barcha so‘rovlar public/index.php ga keladi: u Composer autoloader ni yuklaydi va bootstrap/app.php dan ilova obyektini oladi. Laravel 12 da bootstrap/app.php markaziy sozlash fayli: marshrut fayllari (withRouting), middleware (withMiddleware) va istisnolarni qayta ishlash (withExceptions) shu yerda ko‘rsatiladi. So‘ng HTTP kernel so‘rovni global middleware lar orqali o‘tkazadi, servis provayderlar (AppServiceProvider) ro‘yxatdan o‘tadi va ishga tushadi, router mos marshrutni topadi, marshrut middleware lari (auth kabi) bajariladi va controller metodi chaqiriladi.
Controller qaytargan natija — View, RedirectResponse, massiv yoki model — Response obyektiga aylantiriladi va middleware lar orqali teskari yo‘nalishda qaytadi. Middleware — so‘rov va javob atrofidagi “qatlam”: autentifikatsiya, CSRF tekshiruvi, til va vaqt mintaqasini o‘rnatish, so‘rovlar sonini cheklash. Middleware biznes-qoida joyi emas: “buyurtmani faqat draft holatida tahrirlash mumkin” qoidasi servis yoki Policy da yashaydi.
Controller metodiga parametrlar Laravel servis konteyneri orqali avtomatik beriladi: StoreOrderRequest $request yozilsa, so‘rov validatsiyadan o‘tkaziladi; OrderService $orders yozilsa, konteyner servis obyektini va uning barcha bog‘liqliklarini yaratadi. Marshrutdagi {order} parametri Order $order turi bilan yozilsa, model avtomatik topiladi (route model binding), topilmasa 404 qaytadi. Bu imkoniyatlar controller ni qisqa va testlanadigan qiladi. Keng tarqalgan xato — Blade ichida so‘rov yuborish (Product::all()) yoki hisob-kitob qilish: ko‘rinish faqat tayyor ma’lumotni chiqaradi.
MVC taqdimot qatlamini tartiblaydi: ma’lumot, ko‘rinish va boshqaruv alohida.
Order, Product — jadval, bog‘lanishlar, turlar (casts).OrderService ga.bootstrap/app.php dan ilova obyektiAppServiceProvider — bog‘lanishlar ro‘yxatdan o‘tadiauth)php artisan route:list — barcha marshrutlar, ularning controller va middleware lari.// routes/web.php Route::get('/orders', [OrderController::class, 'index']) ->name('orders.index'); // app/Http/Controllers/OrderController.php class OrderController extends Controller { public function index(): View { $orders = Order::with('counterparty') ->latest() ->paginate(20); return view('orders.index', ['orders' => $orders]); } }
GET /orders → 200 OK, text/html SQL: select * from orders order by created_at desc limit 20 SQL: select * from counterparties where id in (3, 7, 12)
->name('orders.index') — nomli marshrut: route('orders.index') bilan URL yasaladiwith('counterparty') — bog‘langan kontragentlar bitta qo‘shimcha so‘rovda olinadilatest() — created_at bo‘yicha kamayish tartibidaview(...) — ko‘rinish nomi va unga beriladigan ma’lumot@extends('layouts.app') @section('content') <table> @foreach ($orders as $order) <tr> <td>{{ $order->number }}</td> <td>{{ $order->counterparty->name }}</td> <td>{{ number_format($order->total, 2, '.', ' ') }}</td> <td>{{ $order->status->value }}</td> </tr> @endforeach </table> {{ $orders->links() }} @endsection
BY-2026-000123 | Baraka savdo MChJ | 1 120 000.00 | confirmed BY-2026-000122 | Nur market | 450 000.00 | draft « 1 2 3 … 7 »
{{ ... }} — chiqish avtomatik ekranlanadi (XSS dan himoya)$order->status->value — enum qiymati — model casts orqali$orders->links() — sahifalash havolalariOrder::where(...) yoki hisob-kitobbootstrap/app.php da: withRouting, withMiddleware, withExceptions.
OrderService $orders parametri qanday beriladi?Laravel servis konteyneri turini ko‘rib obyektni va uning bog‘liqliklarini avtomatik yaratadi (dependency injection).
Middleware — HTTP so‘rov atrofidagi umumiy qatlam; qoida esa API, import, konsol buyrug‘ida ham ishlashi kerak, shuning uchun servis yoki Policy da yashaydi.
Fowler ta’riflari · interfeys va realizatsiya · konteynerda bog‘lash · qachon kerak
Service Layer (servis qatlami) — Martin Fowler ta’rifi bo‘yicha, ilova chegarasini mavjud amallar to‘plami bilan belgilaydigan va har bir amalda ilovaning javobini muvofiqlashtiradigan qatlam. Oddiy tilda: har bir biznes-amal (buyurtma yaratish, tasdiqlash, rezerv, hisob-faktura chiqarish) — servis klassining bitta ochiq metodi. U tranzaksiyani ochadi, modellar va boshqa servislarni chaqiradi, invariantlarni tekshiradi, hodisa yuboradi. Controller, API controller, Artisan buyrug‘i va import — barchasi bir xil OrderService::confirm() ni chaqiradi.
Repository — domen obyektlariga kolleksiyaga o‘xshash interfeys orqali kirishni ta’minlaydigan, domen va ma’lumotlarni xaritalash qatlami o‘rtasidagi vositachi. Laravel da Eloquent Active Record namunasini amalga oshiradi: model o‘zi saqlanadi ($product->save()), o‘zi so‘rov yasaydi (Product::where()). Shuning uchun har bir model uchun repository yozish ko‘pincha ortiqcha. Repository foydali bo‘ladigan holatlar: murakkab va qayta ishlatiladigan o‘qish so‘rovlari (lowStock()), manbani almashtirish ehtimoli (baza o‘rniga 1C API), servisni bazasiz testlash. OmborPro da faqat ProductRepository bor — katalog bo‘yicha murakkab so‘rovlar uchun.
Bog‘liqlik in’ektsiyasi (dependency injection): sinf o‘ziga kerakli obyektlarni o‘zi new bilan yaratmaydi, ularni konstruktor orqali oladi. Servis ProductRepository interfeysiga bog‘lanadi, aniq EloquentProductRepository ga emas. Qaysi realizatsiya berilishini Laravel servis konteyneri hal qiladi: AppServiceProvider::register() da $this->app->bind(ProductRepository::class, EloquentProductRepository::class) yoziladi. Testda esa xuddi shu interfeysni amalga oshiruvchi soxta (fake) sinf beriladi. Bu SOLID dagi bog‘liqlik inversiyasi tamoyili (Dependency Inversion): yuqori darajali modul past darajali tafsilotga emas, abstraksiyaga bog‘lanadi.
Keng tarqalgan xatolar: repository Eloquent Builder ini qaytaradi va so‘rov yasash servis yoki controller ga “oqib” chiqadi (abstraksiya ma’nosiz bo‘ladi); repository ga biznes-qoidalar qo‘shiladi (u faqat o‘qish va saqlash uchun); servis HTTP ga oid narsalarni qaytaradi (redirect(), response()->json()) — u model yoki DTO qaytarishi, xatoni istisno bilan bildirishi kerak; servis ichida new StockService() bilan bog‘liqlik qattiq kodlanadi.
Service Layer — “nima qilinadi”, Repository — “qayerdan olinadi”.
OrderService::create(), confirm(), cancel(); tranzaksiya va muvofiqlashtirish.findBySku(), lowStock(); SQL tafsilotini yashiradi.interface ProductRepository { public function findBySku(string $sku): ?Product; public function lowStock(int $warehouseId): Collection; } final class EloquentProductRepository implements ProductRepository { // findBySku(): return Product::where('sku', $sku)->first(); public function lowStock(int $warehouseId): Collection { return Product::query() ->join('stocks', 'stocks.product_id', '=', 'products.id') ->where('stocks.warehouse_id', $warehouseId) ->whereRaw('stocks.quantity - stocks.reserved < min_stock') ->get(['products.*']); } }
select products.* from products inner join stocks on stocks.product_id = products.id where stocks.warehouse_id = ? and stocks.quantity - stocks.reserved < min_stock
null — qaror servisda qabul qilinadiBuilder emas// app/Providers/AppServiceProvider.php class AppServiceProvider extends ServiceProvider { public function register(): void { $this->app->bind( ProductRepository::class, EloquentProductRepository::class, ); } } final class OrderService // app/Services/OrderService.php { public function __construct( private ProductRepository $products, private StockService $stock, ) {} }
app(OrderService::class)
→ new OrderService(
new EloquentProductRepository(),
new StockService(...)
)$this->app->bind — interfeys → realizatsiya: har safar yangi obyekt$this->app->singleton() — bitta umumiy obyektinterface ProductRepository { public function price(string $sku): ?int; } final class FakeProducts implements ProductRepository { private array $rows = ['UN-001' => 15000, 'SH-002' => 9000]; public function price(string $sku): ?int { return $this->rows[$sku] ?? null; } } function narx(ProductRepository $repo, string $sku, int $qty): int { $p = $repo->price($sku) ?? throw new DomainException("$sku yo‘q"); return $p * $qty; } echo narx(new FakeProducts(), 'SH-002', 3), "\n";
27000
ProductRepository $repo — funksiya qaysi realizatsiya kelishini bilmaydithrow ifoda sifatidalowStock)find, all, save nusxasiBuilder qaytaradigan “yupqa qobiq”Service Layer biznes-amallarni (jarayon, tranzaksiya) boshqaradi; Repository domen obyektlarini o‘qish va saqlashni yashiradi.
AppServiceProvider::register() da $this->app->bind(ProductRepository::class, EloquentProductRepository::class).
Builder emas, tayyor natija qaytarishi kerak?Aks holda so‘rov yasash servis va controller ga chiqib ketadi, abstraksiya ma’nosiz bo‘ladi va realizatsiyani almashtirib bo‘lmaydi.
Ma’lumot uzatish obyekti · readonly xossalar · tranzaksiya chegarasi · DB::transaction
DTO (Data Transfer Object — ma’lumot uzatish obyekti) — qatlamlar orasida ma’lumotni tashish uchun mo‘ljallangan, xatti-harakatsiz (yoki deyarli xatti-harakatsiz) oddiy obyekt. Controller servisga $request->all() massivini emas, OrderData obyektini beradi. Afzalliklari: maydonlar va turlar aniq (IDE yordam beradi, Larastan tekshiradi), servis HTTP ga bog‘lanmaydi (xuddi shu OrderData ni import yoki API ham yaratadi), noto‘g‘ri kalit (counterpartyid) darhol xato beradi. OmborPro da App\DTO\OrderData va OrderItemData.
DTO o‘zgarmas (immutable) bo‘lishi kerak: yaratilgandan keyin qiymati o‘zgarmaydi, shuning uchun uni bir necha joyga xavfsiz uzatish mumkin. PHP 8.1 da buning uchun readonly xossalar ishlatiladi: public readonly int $counterpartyId. (PHP 8.2 dagi readonly class sintaksisi qisqaroq, lekin biz 8.1 bilan moslikni saqlaymiz.) DTO ni yaratish uchun nomlangan fabrika metodlari yoziladi: fromRequest(StoreOrderRequest $r), fromArray(array $row). Ular kirish ma’lumotini turga keltiradi: forma va JSON dan kelgan "5" satri (int) bilan butun songa aylantiriladi.
Unit of Work (ish birligi) — Fowler ta’rifi: biznes-tranzaksiya davomida o‘zgargan obyektlar ro‘yxatini yuritadigan va ularni bazaga yozishni hamda parallel o‘zgarishlar muammosini muvofiqlashtiradigan obyekt. Doctrine ORM (Symfony) da bu ochiq ko‘rinadi: EntityManager o‘zgarishlarni yig‘adi va flush() da bitta tranzaksiyada yozadi. Eloquent da alohida Unit of Work yo‘q — har bir save() darhol SQL yuboradi. Shu sababli Laravel da ish birligi chegarasini tranzaksiya bilan belgilaymiz: DB::transaction(function () { ... }) ichidagi barcha yozuvlar yoki birga saqlanadi (COMMIT), yoki istisno bo‘lsa birga bekor qilinadi (ROLLBACK).
Tranzaksiya chegarasi servis metodida bo‘ladi, controller yoki modelda emas: “buyurtma + qatorlar + rezerv + ombor harakati” — bitta biznes-amal, demak bitta tranzaksiya. DB::transaction ning ikkinchi argumenti — deadlock (o‘zaro blokirovka) bo‘lganda qayta urinishlar soni: DB::transaction($fn, 3). Keng tarqalgan xatolar: tranzaksiya ichida tashqi HTTP so‘rov yoki e-mail yuborish (ROLLBACK bo‘lsa ham xat ketib qoladi — buning uchun afterCommit hodisalari yoki navbatlar ishlatiladi); istisnoni tranzaksiya ichida “yutib yuborish” (catch dan keyin hech narsa qilmaslik) — shunda ROLLBACK bo‘lmaydi; tranzaksiya natijasini return qilishni unutish.
DTO ma’lumotni qatlamlar orasida tashiydi, Unit of Work esa o‘zgarishlarni bitta tranzaksiyaga yig‘adi.
OrderData, OrderItemData — $request->all() o‘rniga.Error.flush()).final class OrderData { public function __construct( public readonly int $counterpartyId, public readonly int $warehouseId, public readonly array $items, // list<OrderItemData> public readonly string $currency = 'UZS', ) {} public static function fromRequest(StoreOrderRequest $r): self { return self::fromArray($r->validated()); } public static function fromArray(array $v): self { return new self((int) $v['counterparty_id'], (int) $v['warehouse_id'], array_map(OrderItemData::fromArray(...), $v['items'])); } }
OrderData {
counterpartyId: 7, warehouseId: 1, currency: "UZS",
items: [OrderItemData { sku: "UN-001", quantity: 5, price: 15000 }]
}validated() — faqat validatsiyadan o‘tgan maydonlar — all() emas(int) — formadan satr keladi: "7" → 7fromArray(...) — PHP 8.1 birinchi darajali callable sintaksisifinal class OrderItemData { public function __construct( public readonly string $sku, public readonly int $quantity, ) {} public static function fromArray(array $a): self { return new self($a['sku'], (int) $a['quantity']); } } $i = OrderItemData::fromArray(['sku' => 'UN-001', 'quantity' => '5']); echo $i->sku, ' x ', $i->quantity, "\n"; try { $i->quantity = 50; } catch (Error $e) { echo $e->getMessage(), "\n"; }
UN-001 x 5 Cannot modify readonly property OrderItemData::$quantity
(int) $a['quantity'] — satr '5' butun songa aylandiException emas, Errorpublic function create(OrderData $data): Order { return DB::transaction(function () use ($data) { $order = Order::create([ 'counterparty_id' => $data->counterpartyId, 'warehouse_id' => $data->warehouseId, 'status' => OrderStatus::Draft, 'currency' => $data->currency, 'created_by' => auth()->id(), ]); foreach ($data->items as $item) { $this->addItem($order, $item); } $order->update(['total' => $order->items()->sum('total')]); return $order; }, 3); }
BEGIN insert into orders (...) values (...) returning id insert into order_items (...) values (...) ×2 update orders set total = 1120000.00 where id = 45 COMMIT -- istisno bo‘lsa: ROLLBACK
return DB::transaction — closure natijasi metod natijasi bo‘ladi — return ni unutmangOrderStatus::Draft — yangi buyurtma doim draft holatidaaddItem() — mahsulot topilmasa istisno → butun buyurtma bekor, 3) — deadlock bo‘lsa 3 martagacha qayta urinadifunction tranzaksiya(array &$db, callable $fn): void { $nusxa = $db; try { $fn($nusxa); $db = $nusxa; echo "COMMIT\n"; } catch (DomainException $e) { echo "ROLLBACK: {$e->getMessage()}\n"; } } $db = ['orders' => 0, 'reserved' => 0]; tranzaksiya($db, function (array &$d) { $d['orders']++; }); tranzaksiya($db, function (array &$d) { $d['reserved'] += 5; throw new DomainException('Qoldiq yetarli emas'); }); echo json_encode($db);
COMMIT
ROLLBACK: Qoldiq yetarli emas
{"orders":1,"reserved":0}$nusxa = $db — o‘zgarishlar nusxa ustida — bu “ochiq tranzaksiya”$db = $nusxa — faqat muvaffaqiyatda asl holatga yoziladi (COMMIT)reserved: 0 — ikkinchi urinishdagi += 5 saqlanmadi — ROLLBACK$request->all() massividan uchta afzalligini ayting.Maydon va turlar aniq; servis HTTP ga bog‘lanmaydi; noto‘g‘ri kalit darhol xato beradi; o‘zgarmas — xavfsiz uzatiladi.
DB::transaction() — servis metodida ish birligi chegarasini belgilaydi.
ROLLBACK bo‘lsa ham xat ketib qoladi; tashqi ta’sirlar COMMIT dan keyin (afterCommit, navbat) bajarilishi kerak.
Laravel 12 skeleti · bootstrap/app.php · tur va modul bo‘yicha guruhlash · Artisan generatorlari
Laravel 12 loyihasining asosiy papkalari: app/ (ilova kodi: Http/Controllers, Models, Providers), bootstrap/ (app.php — ilovani sozlash), config/ (sozlamalar), database/ (migrations, factories, seeders), public/ (index.php va statik fayllar — veb-server faqat shu papkani ko‘radi), resources/ (Blade, CSS, JS), routes/ (web.php, console.php), storage/ (loglar, yuklangan fayllar, kesh), tests/, vendor/ (Composer paketlari — repozitoriyga qo‘shilmaydi). Avtoyuklash PSR-4 bo‘yicha: composer.json dagi "App\\": "app/" qoidasi App\Services\OrderService sinfini app/Services/OrderService.php faylidan topadi.
Laravel 12 skeleti oldingi versiyalardan ancha ixcham: app/Http/Kernel.php va app/Console/Kernel.php yo‘q — middleware, marshrutlar va istisnolar bootstrap/app.php da sozlanadi; standart holatda faqat AppServiceProvider qoladi; routes/api.php dastlab yo‘q va php artisan install:api buyrug‘i bilan qo‘shiladi; ko‘p konfiguratsiya fayllari yashirilgan, kerak bo‘lsa php artisan config:publish bilan chiqariladi. Standart ma’lumotlar bazasi — SQLite; biz uni PostgreSQL ga almashtiramiz (amaliy mashg‘ulot).
O‘z kodimiz uchun papkalar qo‘shamiz: app/Services, app/DTO, app/Repositories, app/Enums, app/Exceptions, keyinchalik app/Jobs, app/Events, app/Policies. Bu — tur bo‘yicha guruhlash (barcha servislar bir joyda). Muqobil yo‘l — modul (soha) bo‘yicha guruhlash: app/Domain/Sales/{Models,Services,DTO}, app/Domain/Warehouse/.... Kichik va o‘rta loyiha uchun tur bo‘yicha guruhlash sodda va Laravel hujjatlariga mos; tizim o‘sib, jamoalar modullar bo‘yicha bo‘linganda modul bo‘yicha guruhlash chegaralarni aniqroq qiladi. Muhimi — tanlangan qoidaga butun jamoa izchil rioya qilishi.
Fayllarni qo‘lda emas, Artisan generatorlari bilan yaratish tavsiya etiladi — ular to‘g‘ri namespace va shablonni qo‘yadi: make:model Product -mfs (model + migratsiya + fabrika + seeder), make:controller OrderController --resource, make:request StoreOrderRequest. Laravel 11 da make:class, make:enum, make:interface, make:trait buyruqlari qo‘shilgan — servis, DTO va repository interfeyslarini ham shu tarzda yaratamiz. Kod uslubi Laravel Pint (./vendor/bin/pint) bilan avtomatik tekislanadi — u Laravel 11 skeletida allaqachon require-dev da bor.
omborpro/ ├── app/ │ ├── DTO/ OrderData, OrderItemData │ ├── Enums/ OrderStatus │ ├── Exceptions/ InsufficientStockException │ ├── Http/ │ │ ├── Controllers/ OrderController │ │ └── Requests/ StoreOrderRequest │ ├── Models/ Product, Order, Stock ... │ ├── Providers/ AppServiceProvider │ ├── Repositories/ ProductRepository │ └── Services/ OrderService, StockService ├── bootstrap/app.php marshrut, middleware, istisnolar ├── database/ migrations, factories, seeders ├── public/index.php yagona kirish nuqtasi ├── routes/ web.php, console.php └── tests/ Feature, Unit
PSR-4: App\Services\OrderService → app/Services/OrderService.php
app/Services — biznes-jarayonlar — har bir amal bitta metodapp/DTO — qatlamlar orasidagi ma’lumot obyektlaripublic/ — veb-serverning ildizi — boshqa papkalar tashqaridan ko‘rinmaydivendor/ — Composer paketlari — .gitignore dause Illuminate\Foundation\Application; use Illuminate\Foundation\Configuration\Exceptions; use Illuminate\Foundation\Configuration\Middleware; return Application::configure(basePath: dirname(__DIR__)) ->withRouting( web: __DIR__ . '/../routes/web.php', commands: __DIR__ . '/../routes/console.php', health: '/up', ) ->withMiddleware(function (Middleware $middleware) { // }) ->withExceptions(function (Exceptions $exceptions) { // })->create();
GET /up → 200 OK (health check marshruti) `php artisan install:api` → api: __DIR__ . '/../routes/api.php' qo‘shiladi
health: '/up' — monitoring va Docker uchun “tirikmisan?” sahifasiapp/Services, app/Models, app/DTOapp/Domain/Sales/{Models,Services,DTO}README.md da yozib qo‘ying va izchil bo‘ling.php artisan make:model Product -mfs php artisan make:controller OrderController --resource php artisan make:request StoreOrderRequest php artisan make:enum Enums/OrderStatus --string php artisan make:interface Repositories/ProductRepository php artisan make:class Services/OrderService php artisan make:class DTO/OrderData
INFO Model [app/Models/Product.php] created successfully. INFO Migration [database/migrations/2026_09_14_..._create_products_table.php] created successfully. INFO Enum [app/Enums/OrderStatus.php] created successfully. INFO Class [app/Services/OrderService.php] created successfully.
-mfs — migratsiya, fabrika va seeder birga yaratiladi--resource — index, create, store, show, edit, update, destroy metodlari--string — satr qiymatli (backed) enummake:class — Laravel 12: oddiy sinf — servis va DTO uchunroutes/api.php qanday paydo bo‘ladi?php artisan install:api buyrug‘i bilan — u faylni yaratadi va bootstrap/app.php ga ulaydi.
App\DTO\OrderData sinfini qaysi fayldan qidiradi?app/DTO/OrderData.php — composer.json dagi "App\\": "app/" qoidasi bo‘yicha.
Tur bo‘yicha: Laravel generatorlari va hujjatlariga mos, qo‘shimcha sozlash kerak emas.
$request->all() o‘rniga.DB::transaction(): hammasi yoki hech narsa; tashqi ta’sirlar COMMIT dan keyin.Har xil sababga ko‘ra o‘zgaradigan kod (HTTP, biznes, saqlash) alohida joyda bo‘lishini.
bootstrap/app.php dagi withMiddleware() da.
Marshrutdagi {order} parametri Order $order turi bo‘yicha avtomatik topiladi, topilmasa 404.
Active Record: model o‘zini saqlaydi va so‘rov yasaydi.
$this->app->bind(Interfeys::class, Realizatsiya::class) — AppServiceProvider::register() da.
Error: Cannot modify readonly property.
DB::transaction($fn, 3) dagi 3 nima?Deadlock bo‘lganda qayta urinishlar soni.
Model yoki DTO; xatoni istisno bilan bildiradi — redirect() yoki JSON javob emas.