Download as PDF, PPTX
Uploaded byLes-Tilleuls.coop
Official "push" and real-time capabilities for Symfony and API Platform (Mercure protocol)
The document discusses Mercure, a modern push protocol designed for real-time updates in web applications, highlighting its advantages over other technologies like WebSocket. It emphasizes features such as full-duplex communication, easy implementation, built-in reconnection support, and compatibility with serverless architectures. Additionally, it provides details on authorization mechanisms, usage with frameworks like Symfony and API Platform, and practical implementation guidance.
More Related Content
Similar to Official "push" and real-time capabilities for Symfony and API Platform (Mercure protocol)
Official "push" and real-time capabilities for Symfony and API Platform (Mercure protocol)
- 1. @dunglas A Modern PushProtocol, Natively Supported by Symfony & API Platform
- 2. @dunglas Kévin Dunglas ❏ Co-founderof Les-Tilleuls.coop ❏ Creator of Mercure, API Platform and a few more things ❏ Symfony Core Team @dunglas
- 3. @dunglas Dev/consulting/training - Lille/Paris ✍Self-managed since 2011 35 people, 1,000% growth in 6 years 👷 ➡ jobs@les-tilleuls.coop Les-Tilleuls.coop
- 4.
- 5. @dunglas Mercure: Push fromServer to Clients ❏ Push notifications ❏ Synchronize connected devices in real-time ❏ Notify users when an async task has finished ❏ Collaborative editing (Google Drive-like) Alternative to WebSocket, socket.io and Pusher
- 6. @dunglas Today’s Use Case:Real-Time UI Updates 1. Some data is changed by a user through a form 2. UIs of all connected devices (webapp, smartphone…) instantly display updated data bit.ly/2H17hN3
- 7.
- 9.
- 10.
- 11. @dunglas Mercure, the Protocol ❏Full-duplex ❏ Built on top of SSEs and HTTP (POST) ❏ Plays well with techs not supporting persistent connections (serverless, PHP…) ❏ Authorization mechanism (private updates) ❏ Built-in reconnection support and retrieving of lost messages ❏ Auto-discoverable, designed for REST and GraphQL APIs ❏ Encryption support
- 12. @dunglas Stream events toclients
- 13.
- 14. @dunglas Why Server-Sent Events? ❏Leverage HTTP/2 (WebSocket doesn’t) ❏ High-level: built-in ❏ re-connection ❏ state reconciliation ❏ Native support in modern browsers ❏ Built on top of HTTP ❏ easy to implement ❏ Pass through all firewalls ❏ Connection-less push proxies (mobile)
- 15. @dunglas © Narayan Prusty Whatis Multiplexing in HTTP/2? HTTP/2 Multiplexing
- 16.
- 17. @dunglas There is aPolyfill for That! SSEs global support (with polyfill): ~100%
- 19.
- 20. @dunglas The Mercure Hub ❏Implements 100% of the Mercure protocol ❏ Fast, written in Go ❏ Works everywhere: static binaries and Docker ❏ Automatic HTTP/2 and HTTPS ❏ CORS support, CSRF protection ❏ Cloud Native (12Factor App) ❏ Open source (AGPL) Managed and on-premise version available! dunglas+mercure@gmail.com
- 21.
- 22.
- 23.
- 24.
- 25.
- 26.
- 27.
- 28.
- 29. @dunglas Official Mercure supportin Symfony
- 30.
- 31. @dunglas Publishing: the MercureComponent
- 32.
- 33. @dunglas Publishing: the MercureComponent
- 34.
- 35.
- 36.
- 37.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44. @dunglas Authorization ❏ Uses JSONWeb Token (JWT) ❏ An update can be intended for one or several targets ❏ Publisher: must be authenticated ❏ Subscriber: ❏ Can be anonymous (if allowed by the config) ❏ Must be authenticated to receive updates intended for targets ❏ Two transports: cookie and Authorization header
- 45. @dunglas JSON Web Tokenand Targets
- 46. @dunglas Publishing or Subscribingto All Targets
- 47. @dunglas Cookie-based Authorization ❏ Setby the app server during the discovery ❏ The app server and the Mercure hub must share the same domain (or subdomain) ❏ Supported by EventSource ❏ Recommended for web browsers
- 48. @dunglas Setting the cookiewith Symfony
- 49. @dunglas HTTP Header-based Authorization ❏Set by the client ❏ Not supported by native EventSource ❏ Supported by the polyfill ❏ Recommended for servers
- 50.
- 52. @dunglas Official server-side andclient-side support
- 53. @dunglas Mercure Support inAPI Platform ❏ New in 2.4 ❏ Built on top of the Symfony integration ❏ Mercure Hub provided with ❏ the Docker setup ❏ the Kubernetes chart ❏ Ready to use
- 54. @dunglas Auto-dispatch of APIEvery Updates POST PUT PATCH and DELETE will trigger a Mercure update
- 55.
- 56. @dunglas Scaffolding a React ProgressiveWeb App This skeleton is provide in the full API Platform distribution
- 57.
- 61. @dunglas Mercure, SF andVue.js? See you in Paris!
- 62. @dunglas 62 Thanks! Questions? @dunglas@coopTilleuls