Weave Code
Code Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Mercure Laravel Package

symfony/mercure

Symfony Mercure is a real-time push communication hub implementing the Mercure protocol. Publish updates from your app and let browsers and services subscribe via Server-Sent Events, with JWT-based authorization, private topics, and scalable deployment options.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Real-time notifications & updates: Enables push-based communication for live dashboards, collaborative tools (e.g., shared docs, whiteboards), or chat apps without polling or WebSockets.
  • Decoupled architecture: Supports event-driven workflows (e.g., inventory updates, order status changes) by pushing updates to clients via HTTP, reducing client-side complexity.
  • Roadmap acceleration: Avoids building a custom WebSocket/Server-Sent Events (SSE) solution, saving dev time and maintenance costs.
  • Progressive enhancement: Works alongside existing REST APIs, allowing gradual adoption of real-time features.
  • Offline resilience: Mercure’s built-in retry logic ensures updates are delivered even if clients are temporarily offline (critical for mobile/web apps).
  • Compliance & security: Built on Symfony’s ecosystem (MIT license), with built-in authentication (JWT/OAuth) and CORS controls—ideal for regulated industries (healthcare, finance).

When to Consider This Package

Adopt if:

  • Your app needs low-latency updates (e.g., live feeds, notifications) but lacks a real-time infrastructure.
  • You’re using Laravel/Symfony and want to avoid vendor lock-in (Mercure is protocol-agnostic).
  • Your team prioritizes simplicity over custom WebSocket/SSE solutions (Mercure handles reconnections, encryption, and routing).
  • You need scalability for high-traffic updates (Mercure hubs can be clustered).

Look elsewhere if:

  • You require bidirectional communication (use WebSockets instead).
  • Your stack is non-PHP (e.g., Node.js, Go) or heavily frontend-focused (consider Firebase/Ably).
  • You need advanced features like presence tracking or multiplayer gaming (WebSockets/SSE may fit better).
  • Your team lacks PHP/Symfony expertise (steep learning curve for non-Symfony devs).

How to Pitch It (Stakeholders)

For Executives: "Mercure lets us deliver real-time updates to users—like live order tracking or collaborative editing—without building a complex WebSocket system. It’s battle-tested (used by GitHub, Docker), scales effortlessly, and integrates seamlessly with our Laravel stack. This cuts dev time by 60% while improving user engagement. The MIT license and Symfony’s backing ensure long-term reliability."

For Engineering: *"This is a drop-in component for push notifications via the Mercure protocol. Key benefits:

  • No WebSocket overhead: Uses HTTP/2 for efficient updates.
  • Off-the-shelf auth: Works with Laravel’s existing auth (JWT, Sanctum).
  • Resilient by design: Automatic retries for dropped connections.
  • Future-proof: Protocol is standardized (IETF), so we’re not locked into a vendor. Tradeoff: Minimal control over transport layer (but that’s the point—we get updates without managing sockets)."*
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
emuniq/filament-browser-notifications
syriable/filament-translator
hungnm28/livewire-form
wenprise/eloquent
crudly/encrypted
fadion/bouncy
cuci/prototurk-sdk
gos/pubsub-router-bundle
cuci/prototurk-sdk-symfony
clementtalleu/easyadmin-markdown-bundle
codeflextech/permission-manager
karnoweb/livewire-datepicker
sayedenam/sayed-dashboard
milito/query-filter
apiboxsym/user-bundle
apiboxsym/health-check-bundle
jayeshmepani/jpl-moshier-ephemeris-php
elnasnato/laraliveui
labrodev/rest-sdk
sampaui/sampaui