Skip to main content

Server-Sent Events in .NET: A Real-Time Update Example with Item API

 



In today's applications, delivering real-time updates to users is crucial for creating engaging experiences. One efficient way to achieve this in a .NET environment is by using Server-Sent Events (SSE). This blog will guide you through implementing SSE using an Item API to push real-time updates to clients.

What are Server-Sent Events?

Server-Sent Events (SSE) allow a server to push updates to clients over HTTP. Unlike WebSockets, which provide full-duplex communication, SSE is a simpler protocol suited for scenarios where updates flow from the server to the client, such as notifications or live content updates.

Why Use Server-Sent Events?

  • Simplicity: SSE is built on standard HTTP protocols, making it easier to implement compared to WebSockets.
  • Automatic Reconnection: The client automatically reconnects if the connection is lost.
  • Text-Based: SSE sends data in plain text, making it easy to parse.

Setting Up the Item API

Let's assume you have a simple Item API with basic CRUD operations. We will extend this API to support real-time updates for item changes.

Step 1: Create the Item Model

First, define the Item model in your .NET application.

public class Item
{
    public int Id { get; set; }
    public string Name { get; set; }
    public decimal Price { get; set; }
}

Step 2: Set Up the Controller

Next, create a controller that manages your items. Add a method for handling SSE connections.

[ApiController]
[Route("api/[controller]")]
public class ItemsController : ControllerBase
{
    private static readonly List<Item> Items = new();
    private static readonly List<HttpResponse> Clients = new();

    [HttpGet]
    public ActionResult<List<Item>> GetItems()
    {
        return Items;
    }

    [HttpPost]
    public ActionResult<Item> CreateItem([FromBody] Item item)
    {
        item.Id = Items.Count + 1;
        Items.Add(item);
        NotifyClients(item);
        return CreatedAtAction(nameof(GetItems), new { id = item.Id }, item);
    }

    // SSE endpoint
    [HttpGet("updates")]
    public async Task GetUpdates()
    {
        Response.ContentType = "text/event-stream";
        Response.Headers.Add("Cache-Control", "no-cache");

        // Add the response to the client list
        Clients.Add(Response);

        // Keep the connection open
        await Response.CompleteAsync();
    }

    private void NotifyClients(Item item)
    {
        foreach (var client in Clients)
        {
            var message = $"data: Item created: {item.Name}, Price: {item.Price}\n\n";
            client.WriteAsync(Encoding.UTF8.GetBytes(message));
        }
        Clients.Clear(); // Clear clients after notifying
    }
}

Step 3: Connecting the Client

In your front-end application (let's say a React app), set up an EventSource to listen for updates.

import React, { useEffect, useState } from 'react';

const ItemList = () => {
    const [items, setItems] = useState([]);
    
    useEffect(() => {
        const eventSource = new EventSource('https://yourapi.com/api/items/updates');

        eventSource.onmessage = (event) => {
            console.log('New event:', event.data);
            // Update the state or UI with the new item data
            // Example: setItems(prevItems => [...prevItems, JSON.parse(event.data)]);
        };

        return () => {
            eventSource.close();
        };
    }, []);

    return (
        <div>
            <h1>Items</h1>
            {/* Render the items list here */}
        </div>
    );
};

export default ItemList;

Step 4: Testing the Implementation

  1. Start your .NET application and ensure the Item API is running.
  2. Open your front-end application that uses the ItemList component.
  3. Use a tool like Postman or curl to make a POST request to create a new item:
POST /api/items
Content-Type: application/json

{
    "Name": "Sample Item",
    "Price": 19.99
}
  1. Watch your front-end application for real-time updates as new items are created.

Conclusion

Server-Sent Events provide a straightforward method for implementing real-time updates in your .NET applications. By utilizing SSE in our Item API, we demonstrated how to push notifications to clients seamlessly. This approach enhances user experience by delivering timely updates without requiring complex setups.

Feel free to expand on this implementation by adding features like error handling, custom event types, or filtering updates based on item changes. Happy coding!

Comments

Popular posts from this blog

Implementing and Integrating RabbitMQ in .NET Core Application: Shopping Cart and Order API

RabbitMQ is a robust message broker that enables communication between services in a decoupled, reliable manner. In this guide, we’ll implement RabbitMQ in a .NET Core application to connect two microservices: Shopping Cart API (Producer) and Order API (Consumer). 1. Prerequisites Install RabbitMQ locally or on a server. Default Management UI: http://localhost:15672 Default Credentials: guest/guest Install the RabbitMQ.Client package for .NET: dotnet add package RabbitMQ.Client 2. Architecture Overview Shopping Cart API (Producer): Sends a message when a user places an order. RabbitMQ : Acts as the broker to hold the message. Order API (Consumer): Receives the message and processes the order. 3. RabbitMQ Producer: Shopping Cart API Step 1: Install RabbitMQ.Client Ensure the RabbitMQ client library is installed: dotnet add package RabbitMQ.Client Step 2: Create the Producer Service Add a RabbitMQProducer class to send messages. RabbitMQProducer.cs : using RabbitMQ.Client; usin...

.NET 10: Your Ultimate Guide to the Coolest New Features (with Real-World Goodies!)

 Hey .NET warriors! 🤓 Are you ready to explore the latest and greatest features that .NET 10 and C# 14 bring to the table? Whether you're a seasoned developer or just starting out, this guide will show you how .NET 10 makes your apps faster, safer, and more productive — with real-world examples to boot! So grab your coffee ☕️ and let’s dive into the awesome . 💪 1️⃣ JIT Compiler Superpowers — Lightning-Fast Apps .NET 10 is all about speed . The Just-In-Time (JIT) compiler has been turbocharged with: Stack Allocation for Small Arrays 🗂️ Think fewer heap allocations, less garbage collection, and blazing-fast performance . Better Code Layout 🔥 Hot code paths are now smarter, meaning faster method calls and fewer CPU cache misses. 💡 Why you care: Your APIs, desktop apps, and services now respond quicker — giving users a snappy experience . 2️⃣ Say Hello to C# 14 — More Power in Your Syntax .NET 10 ships with C# 14 , and it’s packed with developer goodies: Field-Bac...

Optional Parameters in C# — Writing Flexible and Clean Methods

Hello, .NET developers! 👋 How often have you created multiple method overloads just to handle slightly different cases? Maybe one method accepts two parameters, another three, and one more adds a flag for debugging? That’s a lot of code duplication for something that can be solved beautifully with optional parameters . Optional parameters in C# let you define default values for method arguments. When a caller doesn’t pass a value, the compiler automatically substitutes the default. This feature helps keep your APIs simple, readable, and maintainable. 🎥 Explore more on YouTube : DotNet Full Stack Dev Understanding Optional Parameters Optional parameters are defined by assigning default values in the method signature. When calling the method, you can omit those parameters if you’re okay with the defaults. Example public class Logger { public void Log(string message, string level = "INFO", bool writeToFile = false) ...