Laravel Wave Laravel Package

Product Decisions This Supports

• Real-time feature bets: Supports notifications, activity feeds, live dashboards, job/progress indicators, status updates, and other one-way server-to-client experiences where users benefit from updates without refreshing.
• Roadmap sequencing: Lets the team ship lightweight real-time value now via SSE, while deferring heavier WebSocket investment until bidirectional, presence, or collaborative features are validated.
• Build vs. buy: A Laravel-native, MIT-licensed option that can reduce reliance on managed services such as Pusher/Ably and avoid building custom SSE infrastructure from scratch.
• Architecture leverage: Fits teams already using Laravel events, queues, and broadcasting abstractions; can reuse existing auth and application patterns rather than introducing a separate real-time platform.
• Prioritization filter: Best for “live updates improve the experience” features—not for core real-time products requiring chat, multiplayer, presence, or low-latency bidirectional messaging.

When to Consider This Package

• Your product is Laravel-based and already uses, or can naturally use, Laravel events/broadcasting.
• The need is primarily one-way, server-to-client updates in browser clients: notifications, dashboards, feeds, progress, alerts.
• You want to avoid a managed real-time vendor and are willing to own SSE connection behavior, auth, load testing, and operational scaling.
• Your expected concurrency is moderate, or you can run behind HTTP/2 and plan for long-lived connections through your load balancer.
• Your team is comfortable owning a smaller-community package and validating maintenance, upgrade, and production-support risk.

Look elsewhere if you need bidirectional messaging, chat, presence, collaborative editing, high-frequency/low-latency updates, binary payloads, native mobile push, massive fan-out, multi-region delivery, or vendor-backed SLAs. Also look elsewhere if your infrastructure cannot tolerate long-lived HTTP connections or if the package’s modest community size is unacceptable for a critical path.

How to Pitch It (Stakeholders)

For executives: This is a low-cost, Laravel-native way to add real-time notifications and live updates without paying for a managed pub/sub service or building SSE infrastructure ourselves. It can improve time-to-market and reduce vendor lock-in, but it is not a replacement for WebSockets in interactive or collaborative products. Treat it as a scoped bet: pilot it on a low-risk feature, measure engagement and operational cost, then decide whether to expand or graduate to a broader real-time platform.

For engineering: The package aligns with Laravel’s broadcasting model and standard browser SSE/EventSource behavior, reducing custom protocol work. The main risks are SSE’s unidirectional nature, connection scaling, auth handling, reconnect behavior, and the package’s smaller ecosystem. Isolate it behind an internal interface, load-test representative concurrency, and keep a WebSocket migration path open for future bidirectional needs.