Introduction

graph TD
    A[IoT Device] -- Sends Data --> B[SignalR Hub]
    B -- Broadcasts Data --> C[Client 1]
    B -- Broadcasts Data --> D[Client 2]
    C -- Sends notification --> B
    D -- Sends notification --> B
    B -- Sends notification --> A

SignalR or more precisely ASP.NET SignalR is a library for building real-time web applications. It allows for two-way communication between clients (web browsers, desktop - mobile) and servers, meaning that both can send and receive messages instantly. Here’s a simpler breakdown of SignalR:

Real-time Communication: Imagine you are in a chat room. When someone sends a message, everyone in the room sees it immediately. SignalR makes this possible for web applications.

Push Notifications: Instead of a web page constantly checking (or polling) for new information, SignalR pushes updates to clients whenever there is new data. This is more efficient and responsive.

Versatile Transport: SignalR automatically chooses the best way to transmit messages. It can use WebSockets if available, which is a fast communication protocol, or fall back to other methods like Server-Sent Events or long polling if necessary.

Connection Management: SignalR handles connection issues smoothly. If a client gets disconnected (like losing Wi-Fi), SignalR will attempt to reconnect automatically without disturbing the user experience.

Scalability: It can be used for large applications. SignalR supports scaling out to multiple servers, managing users effectively even in a high-traffic environment.

I intend to use implement servers and clients in C# itself for my personal reasons.

But mostly clients are of Javascript flavours.