---
title: "#server-sent-events articles | Hashnode"
description: "Explore 35 articles tagged #server-sent-events on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/server-sent-events"
---

Tag

# #server-sent-events

35 posts · 0 followers

[Alen Joy](https://hashnode.com/@alenj) · [Aug 13](https://hashnode.com/posts/streaming-chat-dotnet-iasyncenumerable-signalr/6a7d3350643087334240718b)

### [The User Stopped Reading at Token Two: Streaming Chat on .NET](https://pragmaticstack.in/streaming-chat-dotnet-iasyncenumerable-signalr?utm_source=hashnode&utm_medium=feed)

The first token landed in 280 milliseconds and the user was already gone by the second one, tab closed, reading the real logs. The model kept generating anyway, billing you for a paragraph nobody will ever see. The fix is not the model. It is the pipe.

17 min read · [pragmaticstack.in](https://pragmaticstack.in/streaming-chat-dotnet-iasyncenumerable-signalr?utm_source=hashnode&utm_medium=feed)

[4](https://hashnode.com/posts/streaming-chat-dotnet-iasyncenumerable-signalr/6a7d3350643087334240718b)

[Mostafa Mahmoud](https://hashnode.com/@buildwithmostafa) · [Aug 3](https://hashnode.com/posts/streaming-llm-tokens-over-sse/6a708ddccf7091ad66b332ed)

### [Streaming LLM Tokens Over SSE in Production](https://buildwithmostafa.hashnode.dev/streaming-llm-tokens-over-sse?utm_source=hashnode&utm_medium=feed)

Why ChatGPT and Claude's "typing" effect is just SSE: the wire format, why EventSource can't call these APIs directly, and the backend relay pattern with a working Spring Boot example

18 min read · [buildwithmostafa.hashnode.dev](https://buildwithmostafa.hashnode.dev/streaming-llm-tokens-over-sse?utm_source=hashnode&utm_medium=feed)

[Anik Sikder](https://hashnode.com/@anik169) · [Jul 27](https://hashnode.com/posts/server-sent-events-sse-when-the-web-learned-to-listen/6a678b84a1a0a498b179d208)

### [Server-Sent Events (SSE): When the Web Learned to Listen](https://aniksikder.hashnode.dev/server-sent-events-sse-when-the-web-learned-to-listen?utm_source=hashnode&utm_medium=feed)

How SSE transformed the web from asking for updates to receiving them instantly, powering live dashboards, notifications, and AI streaming.

9 min read · [aniksikder.hashnode.dev](https://aniksikder.hashnode.dev/server-sent-events-sse-when-the-web-learned-to-listen?utm_source=hashnode&utm_medium=feed)

[Coding Droplets](https://hashnode.com/@codingdroplets) · [Jul 9](https://hashnode.com/posts/signalr-long-polling-websockets-fallback/6a4f9b5800d2337da2c7fe73)

### [SignalR Falls Back to Long Polling in ASP.NET Core: Causes and Fix](https://codingdroplets.hashnode.dev/signalr-long-polling-websockets-fallback?utm_source=hashnode&utm_medium=feed)

SignalR using long polling instead of WebSockets in ASP.NET Core? Learn why it falls back, how to diagnose it, and how to force WebSockets.

11 min read · [codingdroplets.hashnode.dev](https://codingdroplets.hashnode.dev/signalr-long-polling-websockets-fallback?utm_source=hashnode&utm_medium=feed)

[Virginia Mwega](https://hashnode.com/@veemwega) · [Jul 6](https://hashnode.com/posts/streaming-agent-responses-over-sse-in-next-js/6a4beaac66592992741ade14)

### [Streaming Agent Responses over SSE in Next.js](https://virginiamwegahashnodedev.hashnode.dev/streaming-agent-responses-over-sse-in-next-js?utm_source=hashnode&utm_medium=feed)

Learn to stream AI responses in Next.js with SSE. Build fast, real-time chat apps and compare SSE with WebSockets.

5 min read · [virginiamwegahashnodedev.hashnode.dev](https://virginiamwegahashnodedev.hashnode.dev/streaming-agent-responses-over-sse-in-next-js?utm_source=hashnode&utm_medium=feed)

[Coding Droplets](https://hashnode.com/@codingdroplets) · [Jul 2](https://hashnode.com/posts/stream-llm-responses-aspnet-core-ichatclient/6a4652ea3c863585cf136477)

### [How to Stream LLM Responses in ASP.NET Core with IChatClient](https://codingdroplets.hashnode.dev/stream-llm-responses-aspnet-core-ichatclient?utm_source=hashnode&utm_medium=feed)

Stream LLM Responses in ASP.NET Core with IChatClient and Server-Sent Events - Real-Time Output, Cancellation and .NET 10 Native SSE.

10 min read · [codingdroplets.hashnode.dev](https://codingdroplets.hashnode.dev/stream-llm-responses-aspnet-core-ichatclient?utm_source=hashnode&utm_medium=feed)

[Gtio](https://hashnode.com/@gtoxlili) · [Apr 14](https://hashnode.com/posts/why-your-go-sse-streams-break-on-reconnect-and-how-to-fix-it-with-redis/69de775a26826c8eb08ec2bf)

### [Why your Go SSE streams break on reconnect (and how to fix it with Redis)](https://gtoxlili.hashnode.dev/why-your-go-sse-streams-break-on-reconnect-and-how-to-fix-it-with-redis?utm_source=hashnode&utm_medium=feed)

I spent a while debugging a problem that turned out to be embarrassingly common. We had a Go service streaming LLM responses over SSE. Worked great — until it didn't. A user refreshes the page mid-generation, and the stream is gone. The backend is st...

3 min read · [gtoxlili.hashnode.dev](https://gtoxlili.hashnode.dev/why-your-go-sse-streams-break-on-reconnect-and-how-to-fix-it-with-redis?utm_source=hashnode&utm_medium=feed)

[Voyager AI](https://hashnode.com/@voyager-ai-177308252) · [Mar 25](https://hashnode.com/posts/spry-with-server-sent-events-sse-real-time-updates-without-websockets/69c46cf0a81a8be0d5fc9993)

### [Spry with Server-Sent Events (SSE): Real-Time Updates Without WebSockets](https://voyager-ai.hashnode.dev/spry-with-server-sent-events-sse-real-time-updates-without-websockets?utm_source=hashnode&utm_medium=feed)

Spry with Server-Sent Events (SSE): Real‑Time Updates Without WebSockets Server‑Sent Events (SSE) provide a simple, efficient way to push real‑time updates from server to client over a single HTTP connection. Unlike WebSockets, SSE is unidirectional ...

9 min read · [voyager-ai.hashnode.dev](https://voyager-ai.hashnode.dev/spry-with-server-sent-events-sse-real-time-updates-without-websockets?utm_source=hashnode&utm_medium=feed)

[Amal Vijayakumar](https://hashnode.com/@amal35) · [Mar 13](https://hashnode.com/posts/websockets-when-to-use-them-avoid-overkill-for-real-time-features/69b450246e27dd07d92cb166)

### [WebSockets: When to Use Them — Avoid Overkill for Real-Time Features](https://amalv35.hashnode.dev/websockets-when-to-use-them-avoid-overkill-for-real-time-features?utm_source=hashnode&utm_medium=feed)

Before you spin up that WebSocket server, read this.

5 min read · [amalv35.hashnode.dev](https://amalv35.hashnode.dev/websockets-when-to-use-them-avoid-overkill-for-real-time-features?utm_source=hashnode&utm_medium=feed)

[APIVerve Team](https://hashnode.com/@apiverve) · [Jan 22](https://hashnode.com/posts/real-time-apis-websockets-vs-server-sent-events/6971a2f9991e086250d91a60)

### [Real-Time APIs: WebSockets vs Server-Sent Events](https://apiverve.hashnode.dev/real-time-apis-websockets-vs-server-sent-events?utm_source=hashnode&utm_medium=feed)

REST is request-response. You ask, server answers, connection closes. Works fine for most things. But chat messages can't wait for you to ask. Stock prices need to push the moment they change. Notifications should appear, not be polled for. Two optio...

10 min read · [apiverve.hashnode.dev](https://apiverve.hashnode.dev/real-time-apis-websockets-vs-server-sent-events?utm_source=hashnode&utm_medium=feed)
