Weave Code
Kafka Bundle Laravel Package
mgid/kafka-bundle
A Symfony bundle that integrates Apache Kafka into PHP applications, providing configuration, service wiring, and helpers for producing and consuming messages within a Symfony project.
Symfony Kafka Bundle
Frequently asked questions about Kafka Bundle
- Is mgid/kafka-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. The repository ships a Symfony Bundle subclass, a dependency-injection Extension and Configuration tree, EventDispatcher hooks, and console commands that assume a Symfony Kernel and FrameworkBundle boot cycle. Laravel does not include symfony/http-kernel or symfony/framework-bundle, so there is no supported way to register it as a Laravel package.
- Can I use mgid/kafka-bundle in a Laravel application?
- Only with a custom adapter layer that you write and maintain. You would need to manually instantiate the Symfony extension, translate its YAML configuration tree into a Laravel config file, and bind producers and consumers into Laravel's service container. Once those Symfony seams are replaced, the bundle's main value—its glue—is the part you have already rewritten, so the economic case is weak.
- How do I install mgid/kafka-bundle in a Laravel project?
- There is no Laravel installation path documented for this package. Composer may resolve the Symfony dependencies, but registering the bundle in Laravel is unsupported because Laravel lacks the Symfony FrameworkBundle boot cycle the bundle expects. Treat it as a library to mine rather than a dependency to install, and verify PHP and symfony/* constraints against your composer.lock first.
- What Kafka client does mgid/kafka-bundle wrap—ext-rdkafka or a pure-PHP client?
- The repository overview does not state which Kafka client it wraps, and the compatibility matrix is undocumented. It most likely wraps ext-rdkafka/librdkafka, but that must be verified before any commitment because the C extension adds build and deployment burden. If it is a pure-PHP client instead, expect slower throughput and weaker delivery semantics.
- Does mgid/kafka-bundle support Laravel 10 or 11, or only Symfony 4, 5, and 6?
- The package is a Symfony bundle, and its PHP and Symfony version constraints are not documented or verified. Laravel 10 and 11 pull in selected Symfony components but not symfony/http-kernel or symfony/framework-bundle, so Symfony version support does not translate into Laravel support. Check the package's composer.json constraints against your pinned illuminate/* and symfony/* versions before attempting integration.
- What are Laravel-native alternatives to mgid/kafka-bundle?
- mateusjunges/laravel-kafka is a Laravel-native package that is actively maintained and should be evaluated first. A first-party adapter over ext-rdkafka behind your own Producer and Consumer contracts is another realistic option, especially if the bundle turns out to be a thin wrapper. Keeping third-party implementations behind internal ports prevents package types from leaking into domain code.
- Is mgid/kafka-bundle production-ready and actively maintained?
- There is no evidence of production use outside the author's organization: zero stars, zero dependents, and an opportunity score of 19 with an overall score of 0.16. There is no community review, no third-party audit, and no observable CVE-monitoring or support commitment. The MIT license is clean and permits fork-and-vendor, which is the only realistic long-term posture if you adopt it.
- How does mgid/kafka-bundle handle offset commits, retries, and dead-letter queues?
- These delivery semantics are not documented in the provided context. You must verify whether it exposes manual versus automatic offset commits, at-least-once versus at-most-once delivery, idempotent producer and transactional support, and whether retry, backoff, poison-message, and dead-letter handling are built in or left to the caller. Do not assume production-grade semantics without reading the source and testing against Redpanda or Kafka locally.
- What are the risks of adding mgid/kafka-bundle to a Laravel project?
- The headline risk is architecture mismatch: it assumes a Symfony Kernel and FrameworkBundle boot cycle that Laravel does not provide. The secondary risk is supply chain and provenance: an unvetted transitive dependency graph, unknown release cadence, no community review, and an undocumented compatibility matrix. A timeboxed spike can determine whether the wrapper is substantive or trivial, and you should isolate any implementation behind App\Kafka\Producer and App\Kafka\Consumer contracts.
- How should I test or spike mgid/kafka-bundle before adopting it in Laravel?
- Run a one-to-two-day timeboxed spike: stand up Redpanda or Kafka locally, then prove one produce and one consume through an Artisan command using a hand-written adapter. Confirm librdkafka is buildable in your base images and CI runners, and test in both FPM and long-running worker containers. If the wrapper proves trivial, implement a first-party adapter over ext-rdkafka or evaluate mateusjunges/laravel-kafka behind an internal port instead.
Weaver
How can I help you explore Laravel packages today?