mateusjunges/laravel-kafka
Laravel Kafka brings a clean Laravel-friendly API for producing and consuming Kafka messages, with an emphasis on developer experience and easier testing. Ideal for integrating Kafka streams and event-driven workflows into your Laravel applications.
Consumer classes are very simple, and it is basically a Laravel Command class. To get started, let's take a look at an example consumer.
<?php declare(strict_types=1);
namespace App\Console\Commands\Consumers;
use Illuminate\Console\Command;
use Junges\Kafka\Facades\Kafka;
use Junges\Kafka\Contracts\MessageConsumer;
use Junges\Kafka\Contracts\ConsumerMessage;
class MyTopicConsumer extends Command
{
protected $signature = "consume:my-topic";
protected $description = "Consume Kafka messages from 'my-topic'."
public function handle()
{
$consumer = Kafka::consumer(['my-topic'])
->withBrokers('localhost:8092')
->withAutoCommit()
->withHandler(function(ConsumerMessage $message, MessageConsumer $consumer) {
// Handle your message here
// For manual commit control, use ->withManualCommit() and call $consumer->commit($message)
})
->build();
$consumer->consume();
}
}
Now, to keep this consumer process running permanently in the background, you should use a process monitor such as supervisor to ensure that the consumer does not stop running.
<x-sponsors.request-sponsor/>
In production, you need a way to keep your consumer processes running. For this reason, you need to configure a process monitor that can detect when your consumer processes exit and automatically restart them. In addition, process monitors can allow you to specify how many consumer processes you would like to run concurrently. Supervisor is a process monitor commonly used in Linux environments and we will discuss how to configure it in the following documentation.
To install supervisor on Ubuntu, you may use the following command:
sudo apt-get install supervisor
On mac, you can use homebrew:
brew install supervisor
Supervisor configuration files are typically stored in the /etc/supervisor/conf.d directory. Within this directory, you may create any number of configuration files that instruct supervisor how your processes should be monitored. For example, let's create a my-topic-consumer.conf file that starts and monitors our Consumer:
[program:my-topic-consumer]
directory=/var/www/html
process_name=%(program_name)s_%(process_num)02d
command=php artisan consume:my-topic
autostart=true
autorestart=true
redirect_stderr=true
stdout_logfile=/var/log/supervisor-laravel-worker.log
stopwaitsecs=3600
Onnce the configuration file has been created, you may update Supervisor configuration and start the processes using the following commands:
sudo supervisorctl reread
sudo supervisorctl update
sudo supervisorctl start my-topic-consumer:*
How can I help you explore Laravel packages today?