HTTP, SSE, WebSocket, or WebTransport
Select a network transport from the communication pattern and fallback requirements.
Default
Use HTTP for request-response work.
- Use SSE for server-to-client events with straightforward reconnect behavior.
- Use WebSocket for broadly supported bidirectional messages.
- Use WebTransport when independent streams or datagrams are required and the support contract permits it.
Decide from direction, ordering, reliability, backpressure, authentication, proxy support, observability, and fallback behavior. Hide transport details behind an application service.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.