dunglas/mercure

Features

• Server-Sent Events - Uses a unidirectional HTTP connection and the Server-Sent Events protocol to push real-time updates to clients.
• Real-Time Data Streaming - Pushes live server-side data updates to connected clients using Server-Sent Events to enable reactive user interfaces.
• High Availability Clustering - Coordinates server nodes in a cluster to ensure continuous service availability and fault tolerance for real-time streams.
• Hub Cluster Scaling - Distributes high-throughput real-time event traffic across multiple broker instances to increase capacity.
• Secure Stream Infrastructure - Manages authorized real-time data streams using cryptographic signatures and encryption to protect sensitive updates.
• HTTP-Based Message Brokers - Functions as a centralized hub that receives data via HTTP requests and dispatches them to subscribers.
• URI Template Filtering - Uses URI templates and wildcards to filter incoming updates and ensure subscribers receive only requested data.
• General-Purpose Pub/Sub Servers - Provides a scalable messaging system that routes topic-based updates from publishers to authorized subscribers.
• Pub/Sub Publishing - Provides the primary mechanism for distributing real-time information to all connected clients using authorized HTTP requests.
• Real-time Event Streams - Streams server-driven data updates to diverse clients using Server-Sent Events as a low-latency alternative to WebSockets.
• Broadcasting Hubs - Functions as a messaging hub that broadcasts real-time data updates to web clients using the SSE protocol.
• Topic-Based Pub/Sub - Implements a messaging pattern where data updates are routed to subscribers based on URI-templated topics.
• HTTPS Topic Subscriptions - Establishes secure HTTPS connections for clients to receive updates based on defined URI templates.
• Request Token Authorizations - Authorizes publishers and subscribers by validating signed tokens provided via headers, cookies, or query parameters.
• JWS Token Authorization - Validates the identity of publishers and subscribers using cryptographically signed JWS tokens for stateless authorization.
• JWT Authentication - Uses JSON Web Tokens to authenticate publishers and subscribers for secure stream access.
• Request Authentications - Verifies the identity of clients using tokens or cookies during HTTP request transmission.
• Access Control - Implements authorization mechanisms to restrict private data stream subscriptions to permitted clients.
• JWT Token Validators - Validates publisher and subscriber identities using cryptographically signed JSON Web Tokens to protect data streams.
• Token-Based Identity Verifications - Validates publishers and subscribers using JWTs with support for external identity provider key sets.
• High-Availability Scaling - Deploys high-availability messaging clusters via Kubernetes to handle large volumes of concurrent real-time connections.
• Event-Driven State Reconciliation - Implements mechanisms to recover missed updates after connection loss by reconciling state based on event identifiers.
• Containerized Server Deployments - Provides a server image for isolated deployment with built-in health checks and security certificate automation.
• Event Streamer Orchestration - Provides a containerized delivery system designed for high-availability clustering and horizontal scaling within Kubernetes.
• Managed Hub Provisioning - Offers a hosted messaging server with managed updates and high-availability clustering to reduce operational overhead.
• Message Broker Clustering - Distributes event traffic across multiple server instances to ensure high availability and horizontal scalability.
• Self-Hosted Deployments - Provides a self-hosted data hub deployable via container orchestration or custom binaries with HTTPS support.
• HTTP/3 Implementations - Supports the HTTP/3 protocol over QUIC to provide multiplexed, encrypted streams for low-latency delivery.
• Event History Persistence - Stores and prunes historical event logs to allow clients to recover missed updates after temporary disconnections.
• Event Recovery Mechanisms - Allows clients to retrieve missed events from a stream using a last-received sequence identifier.
• Message - Encrypts payloads using JSON Web Encryption to prevent the hub from accessing update data.
• Network Transmission Security - Encrypts traffic using TLS and supports end-to-end encryption via JWE and authorized topic selectors.
• Event-Driven Architectures - Implements a reactive architecture where a centralized hub broadcasts data updates to authorized subscribers.
• Subscription Lifecycle Monitoring - Tracks the creation and termination of active data stream subscriptions and their listeners.
• User Presence Monitoring - Monitors and broadcasts the connection status of users to provide a real-time list of active clients.
• HTTP/2 Transport Layers - Leverages HTTP/2 and HTTP/3 binary framing and multiplexing for efficient, low-latency data stream delivery.
• Web Framework Integrations - Provides adapters and middleware to connect application events to real-time delivery channels within web frameworks.
• Messaging Systems - Server and library for dispatching updates via Mercure.
• Messaging - Listed in the “Messaging” section of the Awesome Go awesome list.
• Messaging Systems - Server and library for real-time updates via Mercure.

Star history