Weave Code
Buzz Laravel Package
practo/buzz
practo/buzz is a Laravel/PHP package that provides a simple, expressive API for adding activity feeds and notifications to your app. It helps you record events, retrieve timelines, and keep users engaged with minimal setup and clean, maintainable code.
PHP's lightweight HTTP client
Frequently asked questions about Buzz
- What is practo/buzz used for in a Laravel application?
- practo/buzz provides a simple publish-subscribe layer for dispatching and handling internal events inside a Laravel app. You define named channels and Buzz routes each published message to the subscribers registered for that channel, so you avoid hand-wiring listeners and service providers. It is aimed at teams that want decoupled in-app communication without adopting a full queue or event-bus stack.
- How do I install practo/buzz with Composer?
- Install it as a normal Composer dependency in your Laravel project, typically with composer require practo/buzz. Because the package ships a Laravel service provider, it should be discovered automatically on modern Laravel versions. Check the package README for any publishable configuration file or additional setup steps.
- Do I need to register the Buzz service provider or facade manually?
- Buzz includes Laravel service provider and facade integration, so registration is usually handled for you. On Laravel versions with package auto-discovery no manual entry in config/app.php is needed. If you are on an older Laravel release or have discovery disabled, add the provider and facade alias yourself as described in the README.
- How does wildcard matching work for Buzz channels?
- Channels are named, and Buzz supports wildcard matching so a subscriber can listen to a family of channels rather than one exact name. That lets you register a single handler for a group of related events while publishers keep using specific channel names. The exact wildcard syntax is defined in the package documentation, so confirm the pattern style before relying on it.
- Can Buzz subscribers be queued for slow or asynchronous handlers?
- Yes. Buzz is queue-aware, so delivery to subscribers that do heavy work can be pushed onto a Laravel queue instead of running inside the request. This keeps publishing fast for the caller while slower handlers run in the background. You will need a working queue driver and worker configured in your application.
- Is there a required payload schema for messages in practo/buzz?
- No. Payloads are configurable and the package does not impose a rigid schema, so you can publish arrays, DTOs, or whatever structure your subscribers expect. The trade-off is that validation and versioning of payloads is your responsibility, so document what each channel sends.
- Which Laravel versions does practo/buzz support?
- The package overview does not state a specific supported Laravel version range, so check the composer.json requirements in the repository before installing. Because it relies on standard Laravel service provider and queue features, it should work on current releases, but verify constraints against your app. Pin a version that matches your framework version in production.
- How do I test Buzz publishers and subscribers in a Laravel app?
- Because routing is driven by named channels, you can publish a message in a test and then assert that the expected subscriber logic ran or that the right side effect occurred. For subscribers that are queued, use Laravel's Queue::fake helper to assert the job was dispatched rather than executed. Keep channel names in constants or config so tests and production code stay in sync.
- What are the alternatives to practo/buzz for Laravel?
- Laravel's built-in events and listeners cover most decoupled in-app communication, and event broadcasting handles real-time delivery to clients. A queue-backed job or a dedicated event bus is another option when you need guaranteed async processing. Buzz is a thinner publish-subscribe layer aimed at teams that find the native event wiring heavier than they need.
- Is practo/buzz actively maintained and safe to use in production?
- The available package information does not state a release cadence, long-term support commitment, or security policy, so review the repository's commit history and open issues before adopting it. Since Buzz is a small layer built on Laravel's own service provider and queue infrastructure, the surface area and dependency risk are limited. Pin the version and cover your critical channels with tests so future changes are easy to absorb.
Weaver
How can I help you explore Laravel packages today?