Reverb Laravel Package

Technical Evaluation

Architecture Fit

Laravel Reverb is a native replacement for Pusher in Laravel applications, leveraging WebSockets for real-time communication. It integrates seamlessly with Laravel’s existing broadcasting infrastructure, making it ideal for:

• Chat applications (1:1 or group messaging)
• Live notifications (e.g., real-time alerts, activity feeds)
• Collaborative tools (e.g., live document editing, multiplayer games)
• Dashboards (real-time data updates, stock tickers, IoT telemetry)

The package replaces the dependency on Pusher’s cloud service, reducing vendor lock-in and operational costs while maintaining compatibility with Laravel’s Broadcast facade and event-driven architecture.

Key architectural strengths: ✅ Laravel-first design – Built for Laravel’s ecosystem (Laravel 12/13 support, Prompts integration). ✅ Redis-backed – Scales horizontally with Redis Pub/Sub, enabling distributed WebSocket handling. ✅ Pusher API compatibility – Supports Pusher’s HTTP API (e.g., pusher:subscribe), easing migration. ✅ Modular – Supports custom channel authorization, rate limiting, and connection limits.

Potential misfits: ⚠ Monolithic Laravel dependency – Not suitable for non-Laravel PHP apps (e.g., Symfony, standalone Lumen). ⚠ Redis requirement – Adds operational complexity if Redis isn’t already in use. ⚠ WebSocket-only – No fallback to HTTP long-polling (unlike Pusher), which may impact legacy browser support.

Integration Feasibility

Reverb is designed for drop-in replacement of Pusher in Laravel apps. The integration path is straightforward for teams already using Laravel’s broadcasting system.

Prerequisites:

• Laravel 12/13 (or 11 with minor adjustments).
• Redis (v6+ recommended) for pub/sub and connection management.
• PHP 8.1+ (PHP 8.5 explicitly supported).

Key integration points:

1. Replace Pusher config (config/broadcasting.php):

   'pusher' => [
       'driver' => 'reverb',
       'key' => env('PUSHER_APP_KEY'),
       'secret' => env('PUSHER_APP_SECRET'),
       'app_id' => env('PUSHER_APP_ID'),
       'options' => [
           'host' => env('REVERB_HOST', '127.0.0.1'),
           'port' => env('REVERB_PORT', 6001),
           'scheme' => env('REVERB_SCHEME', 'http'),
           'datacenter' => false,
           'use_tls' => env('REVERB_SCHEME') === 'https',
           'activity_timeout' => 60,
           'heartbeat' => 10,
       ],
   ],
   

2. Install Reverb (via Laravel’s reverb:install Artisan command):

   composer require laravel/reverb
   php artisan reverb:install
   

3. Update client-side JS (if using Pusher JS SDK):
   • Replace Pusher with Reverb (or keep using Pusher JS with Reverb’s HTTP API).
   • Example:

     import Reverb from 'laravel-reverb';
     const reverb = new Reverb({
       key: process.env.MIX_PUSHER_APP_KEY,
       wsHost: window.location.hostname,
       wsPort: 6001,
       forceTLS: window.location.protocol === 'https:',
       enabledTransports: ['ws', 'wss'],
     });
     

Compatibility with existing Laravel features:

• Events: Works with Laravel’s Event system (e.g., broadcast(new MessageSent($message))).
• Channels: Supports private/authenticated channels via Laravel’s BroadcastsOn trait.
• Presence Channels: Full support for tracking online users (e.g., App\Models\User::class).
• Echo: Compatible with Laravel Echo (with minor config updates).

Technical Risk

Critical questions for stakeholders:

1. Is Redis already in use? If not, evaluate the operational overhead of adding it.
2. What’s the expected scale? (e.g., 1K vs. 100K concurrent WebSocket connections).
3. Are there legacy clients using Pusher’s HTTP API? Reverb supports it, but testing is required.
4. How will failures be monitored? (e.g., WebSocket disconnections, Redis lag).
5. Is there a fallback plan for WebSocket outages? (e.g., server-sent events as a backup).

Integration Approach

Stack Fit

Reverb is optimized for Laravel’s stack and integrates cleanly with:

• Backend: Laravel 12/13 + PHP 8.1+.
• Database: Redis (required for pub/sub and connection management).
• Frontend: Laravel Echo + JavaScript (Pusher JS SDK with config tweaks).
• DevOps: Docker (official laravel/reverb image), Kubernetes (horizontal scaling), or Laravel Forge.

Non-Laravel compatibility:

• PHP Frameworks: Not directly compatible with Symfony, Lumen, or standalone PHP (requires custom integration).
• Non-PHP Backends: Requires a Laravel API layer to proxy WebSocket traffic.

Migration Path

Rollback Plan:

• Maintain Pusher as a secondary broadcaster (if using HTTP API).
• Use feature flags to toggle between Pusher and Reverb.

Compatibility