Weave Code
Clusteer Laravel Package
renoki-co/clusteer
Clusteer is a Laravel package for running Laravel Echo Server in a clustered setup, letting you scale WebSocket broadcasting across multiple nodes with shared Redis and a load balancer while simplifying configuration for horizontally scaled real-time apps.
Clusteer is a Puppeteer wrapper written for Laravel, with the super-power of parallelizing pages across multiple browser instances.
Frequently asked questions about Clusteer
- What is renoki-co/clusteer used for in Laravel?
- The repository overview describes Clusteer as a Laravel Puppeteer wrapper that parallelizes pages across multiple browser instances for automation workloads. Some package notes also describe clustered Echo Server or coordination scenarios, so confirm the README for your exact use case. Evaluate it for browser automation first and verify any clustering claims before relying on it.
- How do I install Clusteer in a Laravel application?
- Install it with Composer using renoki-co/clusteer, then follow the README for service-provider registration, configuration publishing, and any required browser or Node dependencies. For clustered or coordination use, configure the documented shared cache backend before running workloads. Verify Composer constraints against your PHP and Laravel versions first.
- Does Clusteer support Laravel 9?
- Version 3.3.0 aligns Clusteer with Laravel 9 and a modern PHP runtime, so Laravel 9 is the primary target for that release. Laravel 8 may be viable if the package's Composer constraints allow it. Laravel 7 and PHP 7.3/7.4 are not supported by 3.3.0 without a platform upgrade.
- What PHP version does Clusteer require?
- Clusteer 3.3.0 targets PHP 8 and later, with PHP 8.0.2 or newer likely needed depending on the exact Composer constraints. It drops PHP 7.3 and 7.4 support. Check composer.json and test the resolved dependency set on your target runtime.
- Can I use Clusteer 3.3.0 on Laravel 7 or PHP 7.4?
- No. Release 3.3.0 is effectively breaking for legacy platforms because it drops PHP 7.3/7.4 and Laravel 7. Either stay on the prior Clusteer release that supports your current platform or sequence a PHP upgrade, Laravel upgrade, and then Clusteer 3.3.0.
- Which cache or lock backend should I use with Clusteer in production?
- For coordination-style workloads, use a production-grade shared cache such as Redis rather than local file or database cache. Cluster correctness depends heavily on the reliability and latency of that backend. Validate behavior in staging with the same cache driver you use in production.
- How does Clusteer behave if Redis or the cache backend is unavailable?
- Cache outages or inconsistency can prevent leadership acquisition, leave stale locks, or create split-brain-like behavior if the backend is not strongly consistent enough for the workload. Define fallback behavior for missed coordination and monitor lock acquisition failures. Test failure scenarios before using it for critical scheduled tasks.
- How should I test Clusteer before deploying to production?
- Validate Composer resolution on your exact PHP and Laravel versions, then run cluster-behavior tests in staging with the production cache backend. Deploy a canary or non-critical scheduled job first before expanding to critical workloads. Check service-provider boot, configuration, and browser/runtime dependencies as part of the test plan.
- What alternatives to Clusteer should I consider?
- For browser automation, direct Puppeteer in Node.js or other Laravel browser-automation packages may be simpler depending on your needs. For clustering or coordination, Laravel cache locks, Redis-backed coordination, or dedicated orchestration tools may be better fits. Confirm whether you need Puppeteer parallelism or cluster coordination before choosing an alternative.
- Is Clusteer maintained and what are the upgrade concerns?
- Clusteer 3.3.0 modernizes support for Laravel 9 and PHP 8, but the release notes are terse, so pin versions and track upstream changelogs. Maintain a clear split between legacy apps on older Clusteer releases and modern apps on 3.3.0. Expect Composer conflicts and upgrade boot failures more often than package logic issues.
Weaver
How can I help you explore Laravel packages today?