Weave Code
Kafka Bundle Laravel Package
limlabs/kafka-bundle
limlabs/kafka-bundle integrates Apache Kafka with Symfony/PHP applications, providing bundle configuration and services for producing and consuming messages. It aims to simplify event-streaming setup and Kafka client wiring for PHP projects.
A simple symfony bundle for kafka
Frequently asked questions about Kafka Bundle
- Can I use limlabs/kafka-bundle in a Laravel application?
- Not as-is. limlabs/kafka-bundle is a Symfony bundle: it registers through the Kernel/Bundle lifecycle and depends on Symfony's DI CompilerPass, Extension, and Configuration tree-builder machinery, none of which exists in Laravel's ServiceProvider and Container model. There is no extra.laravel.providers hook, no Illuminate contracts, and no published facade, so Composer will install it but it cannot be booted inside a Laravel app. The realistic options are reusing its framework-agnostic classes or wiring the underlying Kafka client yourself.
- How do I install limlabs/kafka-bundle in a Laravel project?
- You can run composer require limlabs/kafka-bundle, but installation is not the problem, bootstrapping is. Laravel will never autoload the bundle's Symfony extension class or merge its configuration tree, so no services are registered and no config keys are read. If you only want the package's plain PHP classes you can require it and instantiate them manually, but check composer.json first to see whether symfony/framework-bundle or symfony/dependency-injection are hard runtime requirements.
- Can I reuse the producer, consumer, and serializer classes from limlabs/kafka-bundle without Symfony?
- Possibly, but it is unverified. Only the classes that are decoupled from the framework can be reused, and the available materials do not confirm whether the producer/consumer wrappers, serializers, and DTOs are free of Symfony coupling. The gating check is composer.json and a quick read of the class constructors: if they type-hint Symfony services or rely on the container, reuse in Laravel stops there. If they are plain PHP, you can bind them manually from a Laravel ServiceProvider.
- What is the cheapest way to add Kafka producing and consuming to a Laravel app if this bundle does not fit?
- Adopt the Kafka client directly and write a thin Laravel ServiceProvider plus a config file. That almost certainly means ext-rdkafka/php-rdkafka or a pure-PHP client such as longlang/phpkafka. This path avoids Symfony coupling entirely, gives you full control over retries, error handling, and consumer loops, and is the approach most teams should evaluate before attempting to reuse bundle internals.
- What Laravel versions does limlabs/kafka-bundle support?
- None explicitly, because it is a Symfony bundle rather than a Laravel package. It ships no Illuminate contracts, no Laravel service provider, and no facade, so there is no Laravel version constraint to check or rely on in composer.json. Any Laravel compatibility you get is whatever you build yourself around the underlying Kafka client.
- What did limlabs/kafka-bundle 1.0.2 change?
- Release 1.0.2 is a single bugfix: it resolves recurring timeouts while consuming Kafka messages. There are no breaking changes, no new features, and no deprecations, so the integration surface is unchanged. The fix matters because stalled consumer loops manifest as stopped partitions and rising consumer lag in production, and anyone who evaluated 1.0.0 or 1.0.1 would have hit it.
- Is limlabs/kafka-bundle production ready and actively maintained?
- Treat it as high risk. Adoption signals are near zero: roughly 2 stars, 0 dependents, and a score of 0.11, with no observable production usage, no third-party bug reports, and effectively no tutorial or Stack Overflow coverage. The bus factor is a single organization, Limmer Laboratories, and two releases do not amount to a support commitment. The MIT license mitigates abandonment because you can fork, but forking is a cost rather than a benefit.
- How do I test a Kafka integration in Laravel when the bundle only ships Symfony services?
- There is no bundle-level test harness you can reuse, because the bundle cannot boot in Laravel. Test the code you actually write: put your producer and consumer behind interfaces, bind fakes or in-memory implementations in Laravel's container, and keep broker interaction confined to a small adapter. Then run an integration test against a real broker in CI, for example a Kafka container, so serialization and consumer-loop behavior are exercised outside of unit tests.
- What are the best alternatives to limlabs/kafka-bundle for Laravel?
- mateusjunges/laravel-kafka is the obvious choice: it is purpose-built for Laravel, has orders of magnitude more adoption, and covers the same producing and consuming ground. If you prefer to own the client layer, use ext-rdkafka or longlang/phpkafka directly behind a small ServiceProvider. Picking limlabs/kafka-bundle for a Laravel app means knowingly accepting integration friction and support risk with no offsetting benefit.
- Should I fork limlabs/kafka-bundle into a Laravel service provider?
- That is the highest-cost option and rarely justified. You would be re-implementing the Symfony DI extension as a Laravel ServiceProvider and then maintaining that fork against upstream changes from a one-organization project. Only consider it if the bundle contains material logic you would otherwise rebuild, such as schema registry integration, retry or dead-letter-queue handling, or health checks. If that logic is absent or thin, start from the Kafka client directly instead.
Weaver
How can I help you explore Laravel packages today?