Pmk2 Cmar Live Bundle Laravel Package

Technical Evaluation

Architecture Fit

• Symfony/Laravel Compatibility: The bundle is built for Symfony (not Laravel natively), but Laravel’s Symfony integration (via symfony/http-kernel) allows partial adoption. Key considerations:

  • Kernel Integration: Laravel’s HttpKernel can host Symfony bundles, but requires explicit configuration (e.g., Kernel::handle() overrides).
  • Dependency Conflicts: PuMuKIT2’s dependencies (e.g., pumukit/core-bundle) may clash with Laravel’s ecosystem (e.g., Doctrine, Twig). A composer merge-plugin or custom vendor namespace may be needed.
  • Event System: PuMuKIT2 relies on Symfony’s event dispatcher. Laravel’s event system is compatible but requires bridge configuration (e.g., Symfony\Component\EventDispatcher\EventDispatcher aliasing).

• Core Functionality:

  • Live Video + Chat: The bundle extends PuMuKIT2’s live-streaming capabilities with a WebSocket-based chat (likely via Ratchet or similar). Laravel’s Laravel Echo/Pusher could replace the chat backend if WebSocket support is desired.
  • Admin UI: The bundle includes an admin interface for managing live streams. Laravel’s admin panels (e.g., Filament, Backpack) could integrate with its APIs or replace the UI layer.

Integration Feasibility

• Modular Adoption:
  • Option 1: Full Symfony Kernel: Spin up a Symfony micro-service alongside Laravel, exposing APIs via Lumen or API Platform.
  • Option 2: Hybrid Integration: Use the bundle’s services/controllers in Laravel via Symfony\Bridge\Laravel\BridgeServiceProvider (if maintained).
  • Option 3: Feature Extraction: Reimplement chat/live-stream logic in Laravel using:
    • Live Video: FFmpeg + Laravel Queues (e.g., spatie/laravel-ffmpeg).
    • Chat: Laravel Echo + Pusher/Ably.
• Database: PuMuKIT2 uses Doctrine ORM. Laravel’s Eloquent can migrate schemas or use Doctrine DBAL for shared tables.

Technical Risk

• High:
  • Bundle Maturity: No stars/dependents, unmaintained (last commit: ?). Risk of breaking changes or abandoned dependencies.
  • Symfony-Laravel Gap: No official Laravel support; requires custom glue code.
  • WebSocket Dependency: Chat functionality may rely on Ratchet/Mercure, which needs Laravel integration (e.g., beyondcode/laravel-websockets).
• Mitigation:
  • Fork & Adapt: Modify the bundle to work with Laravel’s service container.
  • API-First Approach: Expose PuMuKIT2 as a headless service and consume via Laravel HTTP clients.
  • Feature Parity: Build equivalents in Laravel (e.g., live-streaming with laravel-livewire + ffmpeg).

Key Questions

1. Why Symfony? Is the bundle’s live-streaming/WebSocket stack superior to Laravel’s alternatives (e.g., Echo + Pusher)?
2. Maintenance Burden: Can the team maintain a dual Symfony/Laravel stack, or should features be reimplemented?
3. Performance: How does PuMuKIT2’s live-streaming compare to Laravel + HLS/DASH (e.g., laravel-vod)?
4. Licensing: GPL-2.0 may restrict proprietary use; confirm compatibility with Laravel’s MIT license.
5. Alternatives: Are there Laravel-native live-streaming solutions (e.g., Mux, Agora) that reduce integration risk?

Integration Approach

Stack Fit

• Current Stack:
  • Laravel: PHP 8.1+, Symfony 6.x components (e.g., HTTP Client, UX).
  • Live Video: FFmpeg, HLS/DASH (if using Laravel-VOD).
  • Chat: Laravel Echo + Pusher/Ably.
• Bundle Fit:
  • Partial Fit: Chat and admin UI could replace Laravel’s solutions if PuMuKIT2’s stack is superior.
  • No Fit: Core live-streaming may not align with Laravel’s ecosystem (e.g., no native WebRTC support).

Migration Path

Compatibility

• Doable but Complex:
  • Symfony Components: Laravel already uses many (e.g., HTTP Client, UX). Overlap is manageable.
  • Doctrine vs. Eloquent: Shared database schema possible but requires migration scripts.
  • WebSockets: PuMuKIT2’s chat likely uses Ratchet. Laravel’s beyondcode/laravel-websockets can replace it.
• Blockers:
  • No Laravel Service Provider: Bundle assumes Symfony’s Container. Requires custom binding.
  • Event System: PuMuKIT2 events may not trigger in Laravel without a dispatcher bridge.

Sequencing

1. Phase 1: API Integration

   • Deploy PuMuKIT2 as a separate service (Docker).
   • Use Laravel’s HTTP client to call PuMuKIT2 APIs for live-streaming/chat.
   • Risk: Tight coupling if APIs change.

2. Phase 2: Hybrid Kernel

   • Load PuMuKIT2 bundle in Laravel via Symfony\Bridge\Laravel\BridgeServiceProvider.
   • Override routes/controllers to fit Laravel’s middleware/auth.
   • Risk: Bundle may break due to Symfony assumptions.

3. Phase 3: Feature Replacement

   • Replace PuMuKIT2’s chat with Laravel Echo.
   • Replace live-streaming with Laravel-VOD or Mux.
   • Risk: Feature parity loss if PuMuKIT2 has unique capabilities.

Operational Impact

Maintenance

• High Overhead:
  • Dual Stack: Managing Symfony + Laravel increases CI/CD complexity (e.g., two composer.json files, separate deployments).
  • Unmaintained Bundle: No community support; fixes require internal effort.
  • Dependency Bloat: PuMuKIT2 may pull in obsolete Symfony 3/4 packages.
• Mitigation:
  • Containerize PuMuKIT2 to isolate dependencies.
  • Fork and modernize the bundle for Laravel/Symfony 6+.

Support

• Limited Vendor Support:
  • No official support; rely on GitHub issues (if any responses).
  • Workarounds: Team must become PuMuKIT2 experts or reimplement.
• Laravel Ecosystem:
  • Prefer Laravel-native solutions (e.g., Filament for admin, Echo for chat) to reduce context switching.

Scaling

• Vertical Scaling:
  • PuMuKIT2’s live-streaming may require dedicated servers (e.g., for WebRTC).
  • Laravel can scale horizontally, but Symfony micro-service adds complexity.
• Horizontal Scaling:
  • Stateless Services: PuMuKIT2’s WebSocket/chat should scale with Redis pub/sub.
  • Database: Shared DB may become a bottleneck; consider read replicas.

Failure Modes

Ramp-Up

• Learning Curve:
  • Symfony Gap: Team must learn PuMuKIT2’s event system, admin UI, and live-streaming stack.
  • Debugging: Cross-stack issues (e.g., Symfony events not firing in Laravel) will require deep integration knowledge.
• **