Mercure Bundle Laravel Package

Product Decisions This Supports

• Real-time feature roadmap: Enables push notifications, live updates, or collaborative editing without polling or WebSockets complexity.
• Build vs. buy: Avoids reinventing Mercure integration (protocol, hub management, security) while maintaining full control over UX and business logic.
• Use cases:
  • Live dashboards (e.g., analytics, monitoring).
  • Chat/messaging apps with instant delivery.
  • Collaborative tools (e.g., shared documents, whiteboards).
  • Server-sent events (SSE) alternative with broader client support.
• Scalability: Supports horizontal scaling via Mercure hubs (e.g., self-hosted or third-party like Mercure.rocks).
• Progressive enhancement: Works alongside existing REST APIs, reducing client-side complexity.

When to Consider This Package

• Adopt if:

  • Your stack is Symfony (or PHP with Mercure integration).
  • You need lightweight real-time updates (lower latency than polling, simpler than WebSockets).
  • Clients include browsers, mobile apps (via SSE), or IoT devices supporting HTTP/2.
  • You prioritize standardized protocols (Mercure is IETF-drafted) over custom solutions.
  • Your team lacks WebSocket expertise but needs real-time features.

• Look elsewhere if:

  • You require bidirectional communication (use WebSockets via Ratchet or similar).
  • Clients are non-HTTP (e.g., desktop apps, legacy systems).
  • You need offline-first sync (consider Firebase or PouchDB).
  • Your team prefers JavaScript-first solutions (e.g., Socket.io, Ably).
  • Compliance mandates self-hosted WebSocket control (Mercure hubs may be third-party).

How to Pitch It (Stakeholders)

For Executives: "MercureBundle lets us deliver real-time updates to users—like live notifications or collaborative features—without the overhead of WebSockets. It’s a lightweight, standards-based solution that integrates seamlessly with Symfony, reducing dev time and infrastructure costs. Think of it as ‘server-sent events on steroids’: faster than polling, simpler than WebSockets, and supported by modern browsers. We can start small (e.g., live dashboards) and scale as needed, with options for self-hosting or cloud hubs. MIT-licensed and backed by the Symfony ecosystem, it’s a low-risk way to add real-time capabilities."

For Engineers: *"This bundle wraps Mercure (a modern, HTTP-based pub/sub protocol) into Symfony, giving us:

• Zero polling: Push updates to clients instantly via HTTP/2.
• Broad compatibility: Works with browsers, mobile apps (via SSE), and even non-browser clients.
• Symfony-native: Uses dependency injection, events, and security components we already know.
• Scalable: Offload hub management to Mercure.rocks or self-host.
• Simple: No need to manage WebSocket connections or STOMP brokers.

Tradeoffs:

• Not for bidirectional comms (use WebSockets if needed).
• Requires HTTP/2 support (but falls back gracefully).
• Hubs may be third-party (but self-hosting is an option).

Next steps:

1. Pilot: Use for a live dashboard or notification feature.
2. Benchmark: Compare latency vs. polling/WebSockets.
3. Scale: Evaluate hub hosting (self vs. Mercure.rocks)."*