- What is martin1982/live-broadcast-bundle used for?
- It is a Symfony bundle that adds real-time broadcasting over Server-Sent Events with topic subscriptions and per-client filtering. You publish messages from services and push them to connected clients without extra infrastructure. It integrates with Symfony dependency injection and the framework event system. It is not a native Laravel package.
- Is martin1982/live-broadcast-bundle compatible with Laravel?
- No native Laravel support is documented. The package is built as a Symfony bundle using dependency injection container configuration and FrameworkBundle conventions, not a Laravel ServiceProvider with publishable config files. Laravel teams should treat it as a Symfony component to extract from or rebuild natively. The technical assessment rates structural fit as poor for a Laravel stack.
- How do I install and configure martin1982/live-broadcast-bundle?
- Install it via Composer, enable the bundle in your Symfony bundles configuration, and set channels or topics in the single bundle config file. Then inject the broadcasting service where you publish messages. Confirm the exact config keys and service IDs in the repository because the provided README excerpt is brief. There is no equivalent Laravel install path.
- Does it support Laravel 10 or Laravel 11?
- There is no evidence of Laravel 10 or Laravel 11 support. The package targets Symfony, and the assessment notes no visible Laravel or current-PHP support evidence. You would need to verify the PHP floor and Symfony version constraints in composer.json. Do not assume Laravel compatibility.
- How does Server-Sent Events broadcasting work in production?
- SSE keeps an HTTP connection open and streams text/event-stream messages to browsers, so no WebSocket server or message broker is required. In production you must account for proxy buffering, load balancer idle timeouts, PHP worker limits, and connection scaling. Long-lived PHP connections can be expensive, so plan capacity and fallback behavior. Test with your actual reverse proxy and hosting model.
- How do topics and subscriber filtering work?
- Clients subscribe to named topics, and the bundle filters broadcasts per client so only matching subscribers receive a message. You publish to a topic from a service, and the bundle routes the payload to connected clients. Custom message handlers let you adapt payload formats. Check the config for topic declarations and the client subscription API.
- Can I publish broadcast messages from any service?
- Yes, the package exposes a service-based API for publishing broadcast messages. You inject the broadcaster into your service or controller and call it after a domain event. This fits Symfony autowiring and event system integration. In Laravel, you would need to bridge or reimplement that service binding.
- What Symfony and PHP versions does it require?
- The exact Symfony and PHP version constraints are not stated in the provided context. Inspect composer.json for symfony/framework-bundle, Doctrine, and the PHP floor. The assessment notes Symfony FrameworkBundle conventions and likely Doctrine persistence, so verify compatibility with your Symfony LTS and PHP runtime before adopting.
- What are the maintenance, security, and testing concerns?
- The assessment cites a single-maintainer bus factor, no visible security policy, and no documented Laravel or current-PHP support. It also flags pinned Facebook Graph API calls in v7.0.5 that require periodic patching as API versions deprecate. Test coverage and CI status are not described, so inspect the repository before adopting. Treat maintenance as active but fragile.
- What alternatives should Laravel teams consider?
- Laravel teams should evaluate native options such as Laravel Reverb, Pusher, or a small custom SSE endpoint. Symfony teams can compare Symfony MercureBundle and Mercure for a maintained SSE and WebSocket hub. The build-versus-buy assessment favors rebuilding for Laravel because the package is a Symfony wrapper with third-party API glue.