Asinxron qayta ishlash
Buxgalter “Oylik savdo hisoboti” tugmasini bosdi: 50 000 qator, tayyorlash 90 soniya. Nima bo‘ladi?
nginx va php-fpm odatda 60 soniyada so‘rovni uzadi. Hozircha javob bermang — taxmin qiling.
Bu ma’ruza oxirida siz quyidagilarni bajara olasiz...
Asinxronlik va navbat arxitekturasi
So‘rov faqat vazifani qo‘yadi, ishni worker bajaradi
Job
Queue (navbat)
queues:reports. Birinchi kelgan — birinchi bajariladi (FIFO).Worker
php artisan queue:work — navbatdan jobni olib, handle() ni chaqiradigan uzoq yashovchi jarayon.202 Accepted
Hisobot so‘rovining ikki yo‘li
✗ Sinxron: hammasi so‘rov ichida
- Controller 90 s davomida SQL va Excel bilan band
- 60 s da nginx 504 qaytaradi — fayl yo‘qoladi
- php-fpm jarayoni band: boshqalar navbatda turadi
- Qayta bosish — ikkinchi og‘ir ish boshlanadi
✓ Asinxron: so‘rov → navbat → worker
- Controller
GenerateSalesReport::dispatch()qiladi - 50 ms da
202 Acceptedqaytadi - Worker jobni bajaradi, xato bo‘lsa qayta urinadi
- Tayyor bo‘lgach — bildirishnoma va yuklab olish havolasi
Navbatni Redis ga ulash
# .env QUEUE_CONNECTION=redis REDIS_CLIENT=phpredis REDIS_HOST=redis REDIS_PORT=6379 REDIS_QUEUE=default REDIS_QUEUE_RETRY_AFTER=90 # Redis ichida navbatni ko‘rish (docker compose exec redis sh) # redis-cli LLEN omborpro_database_queues:reports
(integer) 3
config/queue.php dagi redis ulanishi tanlanadipredis/predis paketi:delayed to‘plamidaREDIS_PREFIX dan olinadi (standart: ilova nomi + _database_).1-bo‘lim yakuni: Asinxronlik va navbat arxitekturasi
Job sinflari va yuborish (dispatch)
GenerateSalesReport — Laravel 12 shabloni
namespace App\Jobs; use App\Models\User; use App\Services\ReportService; use Illuminate\Contracts\Queue\ShouldQueue; use Illuminate\Foundation\Queue\Queueable; class GenerateSalesReport implements ShouldQueue { use Queueable; public function __construct( public User $user, public string $from, public string $to, ) {} public function handle(ReportService $reports): void { $reports->exportSales($this->user, $this->from, $this->to); } }
$ php artisan make:job GenerateSalesReport INFO Job [app/Jobs/GenerateSalesReport.php] created successfully.
User sinfi va id yoziladi, worker modelni qayta o‘qiydiController faqat vazifani qo‘yadi
public function store(Request $request): JsonResponse { $data = $request->validate([ 'from' => ['required', 'date'], 'to' => ['required', 'date', 'after_or_equal:from'], ]); GenerateSalesReport::dispatch( $request->user(), $data['from'], $data['to'], )->onQueue('reports'); return response()->json([ 'message' => 'Hisobot tayyorlanmoqda', ], 202); }
HTTP/1.1 202 Accepted
{"message": "Hisobot tayyorlanmoqda"}200 emasdelay, afterCommit, dispatchIf, chain
// 5 daqiqadan keyin bajarilsin SendLowStockAlert::dispatch()->delay(now()->addMinutes(5)); // tranzaksiya muvaffaqiyatli commit bo‘lgandan keyingina DB::transaction(function () use ($order) { $this->stock->ship($order); SendLowStockAlert::dispatch()->afterCommit(); }); // shart bajarilsa SendLowStockAlert::dispatchIf($order->items()->exists()); // ketma-ket: biri yiqilsa, keyingisi ishga tushmaydi Bus::chain([ new GenerateSalesReport($user, '2026-10-01', '2026-10-31'), new SendLowStockAlert(), ])->onQueue('reports')->dispatch();
Redis: queues:default:delayed ← 1 job (5 daqiqa) Redis: queues:default ← commit dan keyin 1 job Redis: queues:reports ← zanjirning 1-jobi
:delayed to‘plamida vaqti kelguncha turadithen/catch/finally; Batchable trait va job_batches jadvali kerakNavbat ichida nima bor: JSON payload
$queue = new SplQueue(); $push = function (string $job, array $data) use ($queue): void { $queue->enqueue(json_encode(['job' => $job, 'data' => $data])); }; $push('GenerateSalesReport', ['user_id' => 7, 'from' => '2026-10-01']); $push('SendLowStockAlert', []); echo 'Navbatda: ' . count($queue) . PHP_EOL; while (!$queue->isEmpty()) { $p = json_decode($queue->dequeue(), true); echo "Bajarildi: {$p['job']} " . json_encode($p['data']) . PHP_EOL; }
Navbatda: 2
Bajarildi: GenerateSalesReport {"user_id":7,"from":"2026-10-01"}
Bajarildi: SendLowStockAlert []2-bo‘lim yakuni: Job sinflari va yuborish (dispatch)
ShouldQueue yozilmasa, dispatch() nima qiladi?SerializesModels modelni navbatga qanday ko‘rinishda yozadi?afterCommit() qaysi xatodan saqlaydi?Workerlar: queue:work, Supervisor, Horizon
queue:work parametrlari
# ishlab chiqish: har job uchun kod qayta yuklanadi (sekin) php artisan queue:listen # production: uzoq yashovchi jarayon php artisan queue:work redis \ --queue=reports,default \ --tries=3 --timeout=60 --sleep=3 \ --max-jobs=500 --max-time=3600 # deploydan keyin: joriy job tugagach workerlar chiqadi php artisan queue:restart
INFO Processing jobs from the [reports,default] queues. 2026-10-27 10:15:02 App\Jobs\GenerateSalesReport ..... RUNNING 2026-10-27 10:15:04 App\Jobs\GenerateSalesReport . 1.84s DONE 2026-10-27 10:15:04 App\Jobs\SendLowStockAlert ....... RUNNING 2026-10-27 10:15:05 App\Jobs\SendLowStockAlert .. 512ms FAIL
reports bo‘shamaguncha default olinmaydiretry_after (90) dan kichik bo‘lishi shart/etc/supervisor/conf.d/omborpro-worker.conf
[program:omborpro-worker] process_name=%(program_name)s_%(process_num)02d directory=/var/www/omborpro command=php artisan queue:work --queue=reports,default --max-time=3600 user=www-data numprocs=2 autostart=true autorestart=true stopasgroup=true killasgroup=true stopwaitsecs=3600 redirect_stderr=true stdout_logfile=/var/www/omborpro/storage/logs/worker.log
$ sudo supervisorctl reread && sudo supervisorctl update $ sudo supervisorctl status omborpro-worker:omborpro-worker_00 RUNNING pid 2114, uptime 0:00:12 omborpro-worker:omborpro-worker_01 RUNNING pid 2115, uptime 0:00:12
--max-time da chiqsa — qayta ishga tushadiHorizon va kuzatiladigan ko‘rsatkichlar
Ko‘rinmaydigan fon jarayoni — eng xavfli jarayon. Navbat to‘xtasa, foydalanuvchi buni bir necha soatdan keyin sezadi.
1Horizon paneli
/horizon: o‘tkazuvchanlik, bajarilish vaqti, muvaffaqiyatsiz joblar, teglar. Faqat Redis bilan ishlaydi.2Kod sifatidagi sozlama
config/horizon.php: supervisorlar, navbatlar, maxProcesses, balance => 'auto'.3Kirish huquqi
viewHorizon Gate: faqat admin roli. Panelda payloadlar ko‘rinadi!4Backlog
5Kutish vaqti
6Deploy
php artisan horizon:terminate — queue:restart o‘rniga.3-bo‘lim yakuni: Workerlar: queue:work, Supervisor, Horizon
queue:restart kerak?--queue=reports,default yozuvida tartib nimani anglatadi?timeout retry_after dan katta bo‘lsa nima bo‘ladi?1-topshiriq: Navbatlar ustuvorligi
Worker --queue=reports,default,low kabi navbatlar ro‘yxati bilan ishga tushirilgan: u avval birinchi navbatni to‘liq bo‘shatadi, keyin ikkinchisiga o‘tadi va h.k. Har bir navbat ichida joblar kelish tartibida (FIFO) olinadi. Joblar ro‘yxati kelish tartibida berilgan: har biri ['id' => int, 'queue' => string]. Worker tinglamaydigan navbatdagi joblar bajarilmaydi. Navbatlar ro‘yxatida takroriy nom bo‘lsa, faqat birinchisi hisobga olinadi. Navbatlar ro‘yxati bo‘sh bo‘lsa — InvalidArgumentException.
Imzo: function navbat_tartibi(array $navbatlar, array $joblar): array
Qaytaradi: Bajarilish tartibidagi job id lari ro‘yxati (list<int>).
navbat_tartibi(['reports', 'default'], [['id' => 1, 'queue' => 'default'], ['id' => 2, 'queue' => 'reports'], ['id' => 3, 'queue' => 'default']])
[2,1,3]
Qayta urinishlar, failed jobs va idempotentlik
tries, backoff, timeout va failed()
class SendLowStockAlert implements ShouldQueue { use Queueable; public int $tries = 5; // jami urinishlar public int $maxExceptions = 3; // istisnolar chegarasi public int $timeout = 60; // retry_after (90) dan kichik public array $backoff = [10, 60, 300]; public function failed(?Throwable $e): void { Log::error('Kam qoldiq xabari yuborilmadi', [ 'error' => $e?->getMessage(), ]); } }
$ php artisan queue:failed 2026-10-27 09:07:41 b1e7c0f2-... redis@default App\Jobs\SendLowStockAlert
Kechikishlar jadvali qanday hisoblanadi
function backoff(int $attempt, array $steps): int { return $steps[$attempt - 1] ?? $steps[count($steps) - 1]; } $steps = [10, 60, 300]; $tries = 5; for ($a = 1; $a <= $tries; $a++) { if ($a === $tries) { echo "$a-urinish: xato -> failed_jobs" . PHP_EOL; break; } $d = backoff($a, $steps); echo "$a-urinish: xato, $d s kutish" . PHP_EOL; }
1-urinish: xato, 10 s kutish 2-urinish: xato, 60 s kutish 3-urinish: xato, 300 s kutish 4-urinish: xato, 300 s kutish 5-urinish: xato -> failed_jobs
failed_jobs va failed()Muvaffaqiyatsiz joblar bilan ishlash
| Buyruq | Vazifasi | Qachon |
|---|---|---|
queue:failed | failed_jobs ro‘yxati: uuid, navbat, sinf, vaqt | Har kuni / alert kelganda |
queue:retry <uuid> | Bitta jobni navbatga qaytaradi | Sabab tuzatilgandan keyin |
queue:retry all | Barcha muvaffaqiyatsizlarni qaytaradi | Tashqi tizim tiklangach |
queue:forget <uuid> | Bitta yozuvni o‘chiradi | Job endi kerak emas |
queue:flush | Barcha yozuvlarni o‘chiradi | Ehtiyotkorlik bilan! |
queue:prune-failed --hours=168 | 7 kundan eski yozuvlarni tozalaydi | Rejalashtirilgan vazifa |
failed_jobs ni cheksiz saqlamang.Bir kunda bitta xabar: ShouldBeUnique + belgi
class SendLowStockAlert implements ShouldQueue, ShouldBeUnique { use Queueable; public int $uniqueFor = 3600; public function handle(ProductRepository $products): void { $key = 'low-stock-alert:' . now()->toDateString(); $items = $products->lowStock(); if ($items->isEmpty() || Cache::has($key)) { return; } $users = User::role('omborchi')->where('is_active', 1)->get(); $note = new LowStockNotification($items->toArray()); Notification::send($users, $note); Cache::put($key, true, now()->endOfDay()); } }
09:00 dispatch → bajarildi, 3 omborchiga xabar 09:00 takroriy dispatch → ShouldBeUnique: navbatga qo‘yilmadi 11:30 queue:retry → Cache::has → return (xabar takrorlanmadi)
4-bo‘lim yakuni: Qayta urinishlar, failed jobs va idempotentlik
2-topshiriq: Qayta urinish yoki failed_jobs?
Job $urinish-urinishda yiqildi (urinishlar 1 dan sanaladi). Job sozlamalari: $tries — jami ruxsat etilgan urinishlar, $backoff — kechikishlar massivi (soniya). Agar $urinish >= $tries bo‘lsa, job muvaffaqiyatsiz (fail). Aks holda qayta uriniladi: kechikish $backoff[$urinish - 1], massiv qisqa bo‘lsa — uning oxirgi elementi, massiv bo‘sh bo‘lsa — 0. $urinish < 1 yoki $tries < 1 bo‘lsa — InvalidArgumentException.
Imzo: function keyingi_qadam(int $urinish, int $tries, array $backoff): array
Qaytaradi: ['action' => 'retry', 'delay' => int] yoki ['action' => 'fail', 'delay' => 0] — kalitlar aynan shu tartibda.
keyingi_qadam(1, 5, [10, 60, 300])
{"action":"retry","delay":10}Vazifalarni rejalashtirish (Task Scheduling)
routes/console.php
use App\Jobs\SendLowStockAlert; use Illuminate\Support\Facades\Schedule; Schedule::job(new SendLowStockAlert()) ->weekdays() ->at('09:00') ->timezone('Asia/Tashkent') ->onOneServer(); Schedule::command('queue:prune-failed --hours=168') ->dailyAt('02:00') ->timezone('Asia/Tashkent'); Schedule::command('rates:fetch') ->cron('30 9 * * 1-5') ->withoutOverlapping() ->appendOutputTo(storage_path('logs/schedule.log'));
$ php artisan schedule:list 0 9 * * 1-5 App\Jobs\SendLowStockAlert ........ Next Due: 21 hours from now 0 2 * * * php artisan queue:prune-failed --hours=168 ... Next Due: 14 hours from now 30 9 * * 1-5 php artisan rates:fetch ......... Next Due: 21 hours from now
0 9 * * 1-5)Ko‘p ishlatiladigan chastota usullari
| Usul | Cron ko‘rinishi | OmborPro misoli |
|---|---|---|
everyFiveMinutes() | */5 * * * * | Dashboard keshini yangilash |
hourly() | 0 * * * * | 1C dan buyurtma holatlarini tortish |
dailyAt('02:00') | 0 2 * * * | Eski loglar va failed jobsni tozalash |
weekdays()->at('09:00') | 0 9 * * 1-5 | Kam qoldiq xabari |
weeklyOn(1, '08:00') | 0 8 * * 1 | Haftalik savdo xulosasi |
monthlyOn(1, '06:00') | 0 6 1 * * | O‘tgan oy hisobotini tayyorlash |
Scheduler production da
Cron qatori
* * * * * cd /var/www/omborpro && php artisan schedule:run >> /dev/null 2>&1Yoki Docker
scheduler servisi: php artisan schedule:work, faqat bitta replikaTekshirish
schedule:list — jadval va keyingi vaqt; schedule:test — darhol sinashKuzatish
appendOutputTo, onFailure, pingOnSuccess — vazifa jim yiqilmasinKo‘p server
onOneServer() + umumiy Redis kesh5-bo‘lim yakuni: Vazifalarni rejalashtirish (Task Scheduling)
->timezone('Asia/Tashkent') yozilmasa va APP_TIMEZONE=UTC bo‘lsa, dailyAt('09:00') Toshkent vaqti bilan qachon ishlaydi?onOneServer() nima uchun kerak va u nimaga tayanadi?3-topshiriq: Cron ifodasi vaqtga mosmi?
Soddalashtirilgan cron ifodasi 5 maydondan iborat: daqiqa (0–59), soat (0–23), oy kuni (1–31), oy (1–12), hafta kuni (0–6, 0 — yakshanba). Har bir maydon vergul bilan ajratilgan qismlardan iborat bo‘lishi mumkin; qism — *, son (9), oraliq (1-5) yoki qadam (*/15: qiymat − maydon minimumi qadamga bo‘linadi). Vaqt Y-m-d H:i formatida. Barcha 5 maydon mos kelsa — true. Maydonlar soni 5 emas yoki vaqt formati noto‘g‘ri bo‘lsa — InvalidArgumentException.
Imzo: function cron_mos(string $ifoda, string $vaqt): bool
Qaytaradi: true — vazifa shu daqiqada ishga tushadi, aks holda false.
cron_mos('0 9 * * 1-5', '2026-10-27 09:00')true
Bildirishnomalar (Notifications)
LowStockNotification: kanallar va database
class LowStockNotification extends Notification implements ShouldQueue { use Queueable; public function __construct(public array $items) {} public function via(object $notifiable): array { return $notifiable->email ? ['mail', 'database'] : ['database']; } public function toArray(object $notifiable): array { return [ 'count' => count($this->items), 'skus' => array_column($this->items, 'sku'), ]; } }
notifications.data = {"count":2,"skus":["UN-001","UN-014"]}database kanali uchun data ustuniga JSONtoMail(): MailMessage quruvchisi
public function toMail(object $notifiable): MailMessage { $mail = (new MailMessage()) ->subject('Kam qoldiq: ' . count($this->items) . ' ta mahsulot') ->greeting("Assalomu alaykum, {$notifiable->name}!") ->line('Quyidagi mahsulotlar minimal qoldiqdan kam:'); foreach (array_slice($this->items, 0, 10) as $i) { $mail->line("{$i['sku']} {$i['name']}: {$i['available']} ta"); } return $mail ->action('Qoldiqlarni ochish', url('/stocks')) ->line('Bu xat OmborPro tomonidan avtomatik yuborildi.'); }
Mavzu: Kam qoldiq: 2 ta mahsulot Assalomu alaykum, Dilshod! Quyidagi mahsulotlar minimal qoldiqdan kam: UN-001 Un 1-nav 50 kg: 4 ta UN-014 Shakar 50 kg: 0 ta [ Qoldiqlarni ochish ]
notify, Notification::send, unreadNotifications
// bitta foydalanuvchiga $user->notify(new LowStockNotification($items)); // rol bo‘yicha ko‘p foydalanuvchiga (spatie/laravel-permission) $users = User::role('omborchi')->where('is_active', true)->get(); Notification::send($users, new LowStockNotification($items)); // tizimda hisobi yo‘q manzilga Notification::route('mail', 'ombor@example.uz') ->notify(new LowStockNotification($items)); // panel: o‘qilmaganlar soni va hammasini o‘qilgan deb belgilash $count = $user->unreadNotifications()->count(); $user->unreadNotifications->markAsRead();
SQL: select count(*) from notifications
where notifiable_id = 7 and read_at is null
→ 3read_at IS NULL bo‘lgan yozuvlar; Livewire qo‘ng‘iroqchasi uchunBildirishnomaga nima beriladi?
✗ Noto‘g‘ri: Eloquent kolleksiyasi
new LowStockNotification($products)— SQL daavailablehisoblangan- Navbatda faqat
Productid lari saqlanadi - Worker modellarni qayta o‘qiydi —
availableyo‘q - Xatda bo‘sh qiymatlar yoki ogohlantirish
✓ To‘g‘ri: kerakli maydonlar massivi
$products->map->only(['sku', 'name', 'available'])- Payload o‘zi to‘liq — bazaga qayta murojaat yo‘q
- Xat aynan voqea paytidagi holatni ko‘rsatadi
- Payload kichik: faqat kerakli maydonlar
6-bo‘lim yakuni: Bildirishnomalar (Notifications)
database kanali ma’lumotni qayerga yozadi va qaysi metod uni quradi?Asosiy xulosalar
1Og‘ir ish — navbatga
dispatch qilib 202 qaytaradi, worker ishni fon rejimida bajaradi.2Job = sinf + seriyalangan parametrlar
ShouldQueue + Queueable; modellar id sifatida saqlanadi, tranzaksiyada afterCommit().3Worker — uzoq yashovchi jarayon
queue:restart, timeout < retry_after.4Xatoga tayyor bo‘ling
tries, backoff, failed() va failed_jobs; sababni tuzatib, keyin queue:retry.5Kamida bir marta ≠ aynan bir marta
6Jadval kodda, xabar kanallarda
routes/console.php da Schedule + Asia/Tashkent; Notification — mail va database.Yakunlashdan oldin sakkizta savol
afterCommit() nima qiladi?--queue=reports,default ma’nosi?$backoff = [10, 60], 4-qayta urinishdan oldin kechikish?10-amaliy mashg‘ulot: 5 ta PHP topshiriq va loyiha bosqichi
Kam qoldiqdagi mahsulotlar
Kam qoldiq xabari matni
Idempotentlik belgisi (Cache::add modeli)
Navbat simulyatori: tries va noyob joblar
Hisobot davrini oylarga bo‘lish (Bus::batch uchun)
Darsni tark etishdan oldin
Javoblaringizni yozing (✎ Javob yozish) yoki qog‘ozga yozib topshiring.
SendLowStockAlert ikki marta bajarilsa, omborchilar ikki xat olmasligi uchun nima qilinadi?