PHPackages                             azizdevfull/laravel-micro-rabbitmq - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Queues & Workers](/categories/queues)
4. /
5. azizdevfull/laravel-micro-rabbitmq

ActiveLibrary[Queues & Workers](/categories/queues)

azizdevfull/laravel-micro-rabbitmq
==================================

High-performance Microservice Event Bus (Pub/Sub) for Laravel using RabbitMQ.

v1.0.0(1mo ago)03↓100%MITPHPPHP ^8.2

Since Apr 7Pushed 2w agoCompare

[ Source](https://github.com/azizdevfull/laravel-micro-rabbitmq)[ Packagist](https://packagist.org/packages/azizdevfull/laravel-micro-rabbitmq)[ RSS](/packages/azizdevfull-laravel-micro-rabbitmq/feed)WikiDiscussions main Synced 1mo ago

READMEChangelogDependencies (6)Versions (5)Used By (0)

🐉 Laravel MicroRabbit
=====================

[](#-laravel-microrabbit)

**MicroRabbit** — bu Laravel mikroxizmatlari (Microservices) uchun yaratilgan, "Enterprise" darajasidagi o'zini-o'zi tiklovchi (Self-Healing) RabbitMQ event-bus kutubxonasi.

U shunchaki xabarlarni jo'natib qabul qilmaydi. U tarmoq uzilishlari, server qulashlari, dublikat xabarlar, zaharli ma'lumotlar (poison payloads) va qotib qolgan jarayonlar ta'sirini keskin kamaytirish uchun mo'ljallangan qudratli yadroga ega.

---

📑 Mundarija
-----------

[](#-mundarija)

- [🐉 Laravel MicroRabbit](#-laravel-microrabbit)
    - [📑 Mundarija](#-mundarija)
    - [📦 1. O'rnatish](#-1-ornatish)
    - [⚙️ 2. Konfiguratsiya (`config/micro-rabbitmq.php`)](#%EF%B8%8F-2-konfiguratsiya-configmicro-rabbitmqphp)
    - [🎧 3. Xabarlarni Qabul Qilish (Consumer)](#-3-xabarlarni-qabul-qilish-consumer)
        - [Atributlar nima qiladi?](#atributlar-nima-qiladi)
    - [📨 4. Xabar Jo'natish (Publish)](#-4-xabar-jonatish-publish)
    - [⏱ 5. RPC - Sinxron Javob Kutish](#-5-rpc---sinxron-javob-kutish)
    - [⚡ 6. Circuit Breaker - Domino Qulashini To'xtatish](#-6-circuit-breaker---domino-qulashini-toxtatish)
    - [🛡 7. Transactional Outbox Pattern](#-7-transactional-outbox-pattern)
    - [🧱 8. Chidamlilik va Himoya (Fault Tolerance)](#-8-chidamlilik-va-himoya-fault-tolerance)
    - [🧪 9. Test Yozish (Faking)](#-9-test-yozish-faking)
    - [💻 10. Konsol Komandalari](#-10-konsol-komandalari)

---

📦 1. O'rnatish
--------------

[](#-1-ornatish)

Kutubxonani Composer orqali loyihangizga qo'shing:

```
composer require azizdevfull/laravel-micro-rabbitmq
```

So'ngra kutubxona sozlamalari (`config`) va Outbox tizimi uchun migratsiyalarni loyihangizga ko'chirib oling:

```
php artisan vendor:publish --tag="micro-rabbitmq-config"
php artisan vendor:publish --tag="micro-rabbit-migrations"
```

Baza jadvallarini yarating:

```
php artisan migrate
```

`.env` faylingizga RabbitMQ ulanish ma'lumotlarini kiriting:

```
MICRO_RABBITMQ_HOST=127.0.0.1
MICRO_RABBITMQ_PORT=5672
MICRO_RABBITMQ_USER=guest
MICRO_RABBITMQ_PASSWORD=guest

# Majburiy emas, qo'shimcha xavfsizlik sozlamalari:
MICRO_RABBITMQ_HEARTBEAT=30
MICRO_RABBITMQ_OUTBOX=false
MICRO_RABBITMQ_MONITORING=true
MICRO_RABBITMQ_PUBLISH_TIMEOUT=5
MICRO_RABBITMQ_OUTBOX_BATCH_SIZE=20
```

`idempotency` va distributed lock funksiyalari uchun production'da `CACHE_DRIVER=redis` tavsiya qilinadi.

---

⚙️ 2. Konfiguratsiya (`config/micro-rabbitmq.php`)
--------------------------------------------------

[](#️-2-konfiguratsiya-configmicro-rabbitmqphp)

Kutubxonani publish qilganingizdan so'ng, loyihangizda `config/micro-rabbitmq.php` fayli paydo bo'ladi. Uning ichidagi asosiy sozlamalar nima vazifa bajarishini bilish juda muhim:

- **`connection.heartbeat`**: *(Default: 30)*. Tarmoq xavfsizlik devorlari (Firewall) jim turgan ulanishni uzib yubormasligi uchun Worker har 30 soniyada RabbitMQ ga "Men tirikman" deb belgi (ping) berib turadi. Bu o'lik ulanishlarning oldini oladi.
- **`features.idempotency`**: Dublikatlardan himoya. Yoqilgan bo'lsa, tizim `message_id` larni keshda saqlaydi va bitta xatni 2 marta o'qimaydi.
- **`features.idempotency_ttl_seconds`**: Idempotency kaliti cache'da qancha vaqt yashashi (Default: `86400` soniya).
- **`features.idempotency_processing_ttl_seconds`**: Worker ishlayotgan paytdagi lock qancha yashashi (Default: `300` soniya).
- **`features.publish_timeout_seconds`**: Oddiy `publish()` broker tasdig'ini maksimal necha soniya kutishi (Default: `5`).
- **`consumer.prefetch_count` / `MICRO_RABBITMQ_PREFETCH`**: Har bir consumer bir vaqtda nechta unacked xabar ushlashini belgilaydi. Throughputni oshiradi, lekin juda katta qiymat fairness va xotira sarfiga salbiy ta'sir qilishi mumkin.
- **`features.publish_confirm_batch_size` / `MICRO_RABBITMQ_PUBLISH_CONFIRM_BATCH`**: Publisher broker confirm'ni har nechta xabardan keyin kutishini belgilaydi. Katta batch odatda publish tezligini oshiradi.
- **`features.publish_confirm_max_wait_ms` / `MICRO_RABBITMQ_PUBLISH_CONFIRM_MAX_WAIT_MS`**: Batch to'lmagan bo'lsa ham necha ms dan keyin confirm flush bo'lishi. Kichik qiymat latency'ni tushiradi, katta qiymat throughput'ni oshirishi mumkin.
- **`features.tracing`**: Yoqilgan bo'lsa, kelgan `trace_id` (yoki yangi UUID) `Context` va `Log::withContext()` orqali barcha log yozuvlariga avtomatik qo'shiladi. Handler ichida alohida hech narsa qilmasdan ELK/Loki da so'rovni oxirigacha kuzatish mumkin bo'ladi.
- **`features.outbox.enabled`**: Transactional Outbox pattern'ni yoqadi. Xatlar to'g'ridan-to'g'ri havo orqali emas, Baza orqali kafolatli jo'natiladi.
- **`features.outbox.max_attempts`**: RabbitMQ o'chib qolsa, Outbox worker xatni jo'natishga necha marta urinishini belgilaydi (Default: 3).
- **`features.outbox.publish_timeout_seconds`**: Outbox relay broker tasdig'ini maksimal necha soniya kutishi (Default: `5`).
- **`features.outbox.batch_size`**: Outbox worker bir aylanishda nechta xabar olishga urinishini belgilaydi (Default: `20`).
- **`paths`**: `micro:cache` qaysi papkalarni skan qilishini belgilaydi. Default: `[base_path('app')]`.
- **`retry.backoff_multiplier`**, **`retry.max_delay_ms`**, **`retry.jitter_ms`**: Retry kechikishining exponential backoff+jitter strategiyasi.
- **`retry.non_retryable_exceptions`**: Qayta urinilmaydigan exception klasslari ro'yxati.
- **`circuit_breaker.enabled` / `MICRO_RABBITMQ_CIRCUIT_BREAKER`**: RPC uchun Circuit Breaker'ni yoqadi/o'chiradi (Default: `true`).
- **`circuit_breaker.threshold` / `MICRO_RABBITMQ_CB_THRESHOLD`**: Nechta ketma-ket xatoda circuit ochiladi (Default: `5`).
- **`circuit_breaker.timeout_seconds` / `MICRO_RABBITMQ_CB_TIMEOUT`**: Circuit ochiq turgan vaqt (soniyada). Bu vaqtdan keyin bitta "probe" request o'tkaziladi (Default: `30`).
- **`monitoring.*`**: Metrika cache'i va alert thresholdlari (`outbox backlog`, `blocked`, `DLQ size`, `publish timeout`) uchun sozlamalar.

Production benchmarklar uchun amaliy boshlang'ich tuning:

```
MICRO_RABBITMQ_PREFETCH=20
MICRO_RABBITMQ_PUBLISH_CONFIRM_BATCH=50
MICRO_RABBITMQ_PUBLISH_CONFIRM_MAX_WAIT_MS=10
```

### Realistic Benchmark Natijalari

[](#realistic-benchmark-natijalari)

**Muhim:** Qisqa "burst" testlarda sun'iy yuqori raqamlar chiqadi. Quyidagi natijalar 5000–25000 xabarlik **sustained load** bilan o'lchangan (1 consumer, SQLite, `prefetch_count=1`):

Workload5 000 xabar10 00015 00020 00025 000`light` (CPU only)238 eps211219211215`db` (INSERT)214 eps214212214212`db_read` (INSERT + SELECT)244 eps229229229216**Asosiy xulosalar:**

- **Haqiqiy bottleneck — `prefetch_count=1`, handler emas.** `light` va `db` workload orasida farq atigi ~3 eps. Sababi: `prefetch=1` bilan consumer har bir xabarni ACK qilmasdan keyingisini ololmaydi — bu RabbitMQ round-trip latency ceiling ni belgilaydi (~215 eps). Handler ichida DB query bo'lsa ham bo'lmasa ham natija bir xil.
- **Kichik testlardagi yuqori raqamlarga ishonmang.** Burst rejimida (100–400 xabar) consumer tayyor xabarlarni oldindan o'qib, 900–1200 eps ko'rsatishi mumkin. Bu real sustained throughput emas.
- **Throughputni oshirish:** `prefetch_count` va consumer worker sonini oshiring:

```
MICRO_RABBITMQ_PREFETCH=20
```

```
# 4 ta parallel consumer
php artisan micro:consume &
php artisan micro:consume &
php artisan micro:consume &
php artisan micro:consume &
```

`prefetch=20` + 4 consumer bilan taxminiy throughput: `215 × 4 × ~3 = ~2500 eps`. Aniq raqam uchun o'z muhitingizda o'lchang.

---

🎧 3. Xabarlarni Qabul Qilish (Consumer)
---------------------------------------

[](#-3-xabarlarni-qabul-qilish-consumer)

MicroRabbit'da xabarlarni qabul qilish uchun config fayllarda marshrutlarni ro'yxatdan o'tkazish shart emas. Tizim PHP 8 Attributes orqali **Auto-Discovery** (o'zini-o'zi topish) xususiyatiga ega.

Default holatda `micro:cache` faqat `base_path('app')` ichini skan qiladi. Agar handlerlar boshqa joyda bo'lsa, `config/micro-rabbitmq.php` dagi `paths` array'iga qo'shib qo'ying.

Shunchaki istalgan papkada bitta Action klass yarating va unga atributlarni qo'shing:

```
namespace App\Actions;

use Azizdev\MicroRabbit\Attributes\ConsumeEvent;
use Azizdev\MicroRabbit\Attributes\MicroConfig;

#[ConsumeEvent(routingKey: 'order.created', queue: 'order_processing_queue', exchange: 'micro_events')]
#[MicroConfig(tries: 5, delayMs: 15000, retry: true)]
class OrderCreatedAction
{
    public function handle(array $payload)
    {
        // 1. Kelgan datani o'qiymiz
        $orderId = $payload['id'];

        // 2. Biznes logikani bajaramiz
        // ...

        // 3. Agar RPC qilingan bo'lsa, Return yozish kifoya, MicroRabbit uni javob qilib qaytaradi!
        return ['status' => 'success', 'processed_at' => now()];
    }
}
```

### Atributlar nima qiladi?

[](#atributlar-nima-qiladi)

1. **`#[ConsumeEvent]` (Majburiy):**
    - `routingKey`: Qaysi nomdagi xatni eshitishi kerakligi (masalan: `user.registered`).
    - `queue`: RabbitMQ da qaysi navbat yaratilishi kerakligi.
    - `exchange`: Qaysi pochtadan kutayotgani (Default: `micro_events`).
2. **`#[MicroConfig]` (Ixtiyoriy):** Worker charchab qolmasligi uchun xatoliklar qoidasi.
    - `tries`: Agar kod xatolik (`Exception`) bersa, necha marta qayta urinish kerak? (Default: 3).
    - `delayMs`: Qayta urinishlar orasida necha millisoniya kutish (uxlash) kerak? (Default: 10000 = 10 sek).
    - `retry`: Qayta urinish tizimini umuman o'chirib qo'yish (`false` bo'lsa, 1-xatodayoq qabristonga ketadi).

**DIQQAT:** Klassni yozib bo'lgach, tizim uni tanib olishi uchun doim keshni yangilang:

```
php artisan micro:cache
```

---

📨 4. Xabar Jo'natish (Publish)
------------------------------

[](#-4-xabar-jonatish-publish)

Xabar jo'natish juda oddiy. Fasaddan foydalanamiz:

```
use Azizdev\MicroRabbit\Facades\MicroRabbit;

// Eng sodda usul:
MicroRabbit::publish('user.registered', [
    'id' => 1,
    'name' => 'Azizbek'
]);
```

*Tizim bu xatga avtomatik ravishda `trace_id`, `message_id` va hozirgi `timestamp` ni qo'shib, xavfsiz tarzda o'rab jo'natadi.*

---

⏱ 5. RPC - Sinxron Javob Kutish
-------------------------------

[](#-5-rpc---sinxron-javob-kutish)

Mikroxizmatlar orasida kimdandir tezkor ma'lumot olish kerak bo'lganda (Sinxron), biz `request` dan foydalanamiz.

**Muammo:** Agar narigi xizmat o'chib yotgan bo'lsa, oddiy tizimlar cheksiz kutib, serverni qotirib qo'yadi. **MicroRabbit Yechimi:** Qat'iy Taymer (Strict Timeout).

```
use Azizdev\MicroRabbit\Facades\MicroRabbit;

try {
    // 3-parametr: 5 soniya kutish taymeri
    $response = MicroRabbit::request('get.user.balance', ['user_id' => 7], 5);

    echo "Foydalanuvchi balansi: " . $response['balance'];

} catch (\Exception $e) {
    // Agar 5 soniyada javob kelmasa yoki narigi servis o'chgan bo'lsa
    // Tizim qulab tushmaydi, balki chiroyli xatolik otadi!
    return response()->json(['error' => 'To\'lov tizimi vaqtinchalik ishlamayapti'], 504);
}
```

---

⚡ 6. Circuit Breaker - Domino Qulashini To'xtatish
--------------------------------------------------

[](#-6-circuit-breaker---domino-qulashini-toxtatish)

**Muammo:** `user-service` o'chib qoldi. Unga har bir RPC so'rov 5 soniya timeout bilan kutadi. Agar 100 ta concurrent so'rov bo'lsa — 100 × 5 soniya = server thread pool to'ladi va boshqa barcha xizmatlar ham ishlashdan to'xtaydi. Bu **Cascading Failure** (Domino qulashi).

**MicroRabbit Yechimi:** Circuit Breaker. Belgilangan miqdorda xato yig'ilsa, tizim o'sha routing key uchun RPC so'rovlarni RabbitMQ ga umuman yubormasdan, **darhol** xato qaytaradi. Thread pool saqlanadi.

```
[CLOSED] → 5 xato → [OPEN] → 30 soniya → [HALF-OPEN] → muvaffaqiyat → [CLOSED]
  ✅ Normal       ❌ Blokli          🔍 Sinov             ✅ Normal

```

```
use Azizdev\MicroRabbit\Facades\MicroRabbit;

try {
    $balance = MicroRabbit::request('get.user.balance', ['user_id' => 7], 5);

} catch (\RuntimeException $e) {
    // Circuit ochiq bo'lsa ham, timeout bo'lsa ham — bu catch ga tushadi
    // $e->getMessage() da "Circuit Breaker" yoki "RPC Timeout" yozuvi bo'ladi
    return response()->json(['error' => 'Balans xizmati vaqtincha mavjud emas'], 503);
}
```

Circuit Breaker **avtomatik ishlaydi** — dasturchi hech narsa qo'shimcha qilmaydi. `.env` orqali sozlanadi:

```
MICRO_RABBITMQ_CIRCUIT_BREAKER=true
MICRO_RABBITMQ_CB_THRESHOLD=5   # 5 ta xatoda circuit ochiladi
MICRO_RABBITMQ_CB_TIMEOUT=30    # 30 soniyadan keyin recovery probe o'tadi
```

> **Eslatma:** Circuit Breaker faqat `request()` (RPC) uchun ishlaydi. Oddiy `publish()` asinxron bo'lgani uchun unga circuit breaker kerak emas.

---

🛡 7. Transactional Outbox Pattern
---------------------------------

[](#-7-transactional-outbox-pattern)

**Dahshatli ssenariy:** Mijozdan pulni yechdingiz, bazaga yozdingiz. Endi RabbitMQ ga xat otayotganingizda server interneti uzildi. Mijozning puli ketdi, lekin xizmat ko'rsatilmadi!

Buning yagona yechimi — Outbox Pattern. `.env` da `MICRO_RABBITMQ_OUTBOX=true` qiling. Endi `MicroRabbit::publish()` havo orqali xat otmaydi, balki uni o'sha vaqtdagi Tranzaksiya bilan birga Bazaga yozib qo'yadi.

```
use Illuminate\Support\Facades\DB;
use Azizdev\MicroRabbit\Facades\MicroRabbit;

DB::transaction(function () use ($user) {
    // 1. Pul yechiladi
    $user->decrement('balance', 50000);

    // 2. Xat bazadagi "micro_outbox" jadvaliga tushadi (Tarmoq uzilsa ham 0% xavf)
    MicroRabbit::publish('payment.success', ['user_id' => $user->id]);
});
```

Bazada yig'ilgan xatlarni tinimsiz ravishda RabbitMQ ga otib turuvchi pochta xizmatini serveringizda (Supervisor orqali) yoqib qo'ying:

```
php artisan micro:outbox:work
```

*Bu Worker RabbitMQ o'chib qolsa ham qulab tushmaydi. U ulanish tiklanishini kutadi va o'zini-o'zi tiklaydi (Auto-Recovery).*

---

🧱 8. Chidamlilik va Himoya (Fault Tolerance)
--------------------------------------------

[](#-8-chidamlilik-va-himoya-fault-tolerance)

Kutubxona "Arvoh" xatolardan quyidagicha himoyalangan:

1. **Idempotency:** RabbitMQ adashib bitta xatni 2 marta jo'natib yuborsa ham, Worker qorovuli xatning ID sini eslab qoladi va 2-martasida uni ignor qiladi.
2. **Kutish Zali (Delayed Retry):** Kodingiz API ga ulana olmay qulasa, worker xatni asrash uchun uni maxsus `_delayed` navbatiga otadi. Xat u yerda masalan 10 soniya uxlaydi va yana asosiy navbatga qaytadi.
3. **Qabriston (DLX - Dead Letter Exchange):** Agar xat 3 marta urinib ham xatolik beraversa, boshqa sog'lom xatlarga xalaqit bermasligi uchun u `_failed` navbatiga (Qabristonga) otib yuboriladi.
4. **Circuit Breaker:** RPC orqali murojaat qilingan xizmat o'chib qolsa, belgilangan xato chegarasidan keyin so'rovlar darhol rad etiladi. Thread pool to'lib qolmaydi, bitta xizmatning o'lishi qolganlarni olib ketmaydi (qarang: [6-bo'lim](#-6-circuit-breaker---domino-qulashini-toxtatish)).
5. **Distributed Tracing (Auto):** `MICRO_RABBITMQ_TRACING=true` bo'lsa, kelgan xabardagi `trace_id` avtomatik ravishda `Log::withContext()` orqali joriy handlerning barcha log yozuvlariga qo'shiladi. ELK/Loki da bitta so'rovni servisdan-servisga kuzatish uchun handler ichida hech narsa yozish shart emas.

Dasturchi xatoni to'g'rilagach, qabristondagi xatlarni bitta komanda bilan yana hayotga qaytarishi mumkin:

```
php artisan micro:retry {navbat_nomi}
```

---

🧪 9. Test Yozish (Faking)
-------------------------

[](#-9-test-yozish-faking)

MicroRabbit bilan Pest yoki PHPUnit orqali test yozish "Oltin Standart" darajasida. Test paytida haqiqiy RabbitMQ ga ulanib vaqt o'tkazmaysiz.

```
use Azizdev\MicroRabbit\Facades\MicroRabbit;

test('buyurtma tasdiqlanganda xat otilishi kerak', function () {
    // 1. Qopqonni yoqamiz (Xatlar RabbitMQ o'rniga xotiraga tushadi)
    MicroRabbit::fake();

    // 2. Asosiy loyihaning mantiqiy qismi ishlaydi
    $this->postJson('/api/orders/confirm', ['id' => 123]);

    // 3. Xat aniq otilganiga ishonch hosil qilamiz
    MicroRabbit::assertPublished('order.confirmed');

    // 4. (Ixtiyoriy) Payload ichidagi datalarni chuqur tekshiramiz
    MicroRabbit::assertPublished('order.confirmed', function ($payload) {
        return $payload['id'] === 123;
    });

    // 5. Ortiqcha boshqa xat ketib qolmaganini tekshiramiz
    MicroRabbit::assertNotPublished('order.failed');
});
```

---

💻 10. Konsol Komandalari
------------------------

[](#-10-konsol-komandalari)

- `php artisan micro:cache` — `paths` bo'yicha attributlarni topib, yashin tezligida ishlashi uchun keshga yozadi. Doim kod o'zgarganda urilishi shart.
- `php artisan micro:consume --queue={queue}` — Event worker'ni ishga tushiradi. `--queue` berilmasa barcha topilgan navbatlarni tinglaydi.
- `php artisan micro:outbox:work` — Outbox pattern yoqilgan bo'lsa, bazadan xatlarni olib uzluksiz RabbitMQ ga otib turuvchi asosiy dvigatel.
- `php artisan micro:retry {queue}` — `_failed` (Qabriston) ga tushib qolgan xatlarni qaytadan ishlash uchun asosiy navbatga qaytaradi.
- `php artisan micro:health` — Outbox backlog, DLQ hajmi va publish timeout metrikalarini tekshiradi.

###  Health Score

41

—

FairBetter than 89% of packages

Maintenance95

Actively maintained with recent releases

Popularity4

Limited adoption so far

Community6

Small or concentrated contributor base

Maturity49

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~0 days

Total

2

Last Release

32d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/3394b6abf97b48e1ad754c6d5664fd8d673175c4d266209f4142d1325f5d54a0?d=identicon)[azizdevfull](/maintainers/azizdevfull)

---

Top Contributors

[![azizdevfull](https://avatars.githubusercontent.com/u/102867709?v=4)](https://github.com/azizdevfull "azizdevfull (38 commits)")

---

Tags

laravelrabbitmqevent buspub-submicroservices

###  Code Quality

TestsPHPUnit

Code StyleLaravel Pint

### Embed Badge

![Health badge](/badges/azizdevfull-laravel-micro-rabbitmq/health.svg)

```
[![Health](https://phpackages.com/badges/azizdevfull-laravel-micro-rabbitmq/health.svg)](https://phpackages.com/packages/azizdevfull-laravel-micro-rabbitmq)
```

###  Alternatives

[bschmitt/laravel-amqp

AMQP wrapper for Laravel and Lumen to publish and consume messages

2752.3M7](/packages/bschmitt-laravel-amqp)[nuwber/rabbitevents

The Nuwber RabbitEvents package

120515.8k3](/packages/nuwber-rabbitevents)[iamfarhad/laravel-rabbitmq

A robust RabbitMQ driver for Laravel Queue with advanced message queuing, reliable delivery, and high-performance async processing capabilities

3215.6k](/packages/iamfarhad-laravel-rabbitmq)[vinelab/bowler

A Rabbitmq wrapper for Laravel

4659.7k1](/packages/vinelab-bowler)[mookofe/tail

RabbitMQ and PHP client for Laravel and Lumen that allows you to add and listen queues messages just simple

5552.5k](/packages/mookofe-tail)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)