2. Real-world story

ArenaLive (sports) needs score pushes during matches. They apply Enterprise Real-Time Systems inside ShopNest.Live so updates appear without refresh.

Outcome: ArenaLive delivers score pushes during matches with a clear SignalR/SSE design.

3. Why it matters

Without solid enterprise real-time systems, users refresh endlessly, servers burn CPU on polling, or messages vanish when you scale to multiple pods.

4. Visual understanding

Read this diagram top to bottom — the mental model for Enterprise Real-Time Systems.

Client needs live data
   ├── Polling / long polling (HTTP, simple, costly)
   ├── WebSockets (duplex, low latency)
   ├── SSE (server→client stream)
   └── SignalR (hubs + auto fallback)

5. Key concepts (easy words)

6. How it works

• Definition: Enterprise Real-Time Systems explains how live updates work before you write SignalR code — pick the right transport for the job.
• Prefer groups/users over global broadcast for multi-tenant data.
• Persist important messages in a database; SignalR is the live pipe, not the source of truth.
• Plan scale-out (Redis or Azure SignalR) before production traffic.

7. SignalR vs SSE vs WebSockets

8. Try this example

Create an ASP.NET Core app with the SignalR package (or an SSE endpoint). Run dotnet run and test in the browser DevTools.

// Choose transport by need
// Duplex chat/tracking → SignalR
// One-way ticker → SSE
// Legacy proxy only → long polling fallback

9. Another real-world angle

10. Best practices checklist

• Use withAutomaticReconnect() on JS/.NET clients.
• Authorize hubs; never trust client-supplied tenant/order ids without checks.
• Keep payloads small; send IDs + deltas, not entire documents.
• Log connectionId and userId for support debugging.
• Load-test concurrent connections before a sale or match day.

11. Common mistakes

• Broadcasting to Clients.All for private order/chat data.
• Scaling to multiple pods without Redis or Azure SignalR.
• Putting secrets or huge payloads on the wire every second.
• Forgetting automatic reconnect on the client.

12. Practice on your machine

1. Create or open ShopNest.Live.Api (ASP.NET Core + SignalR package).
2. Apply the Enterprise Real-Time Systems pattern from the example.
3. Run the app and open a test client (JS SignalR client or EventSource).
4. Confirm one successful push in DevTools Network.
5. Note how you would scale this (single node vs Redis/Azure SignalR).

Experiments

• Change the hub method or event name and update the client to match.
• Send to a group instead of All (or the reverse) and observe who receives it.
• Disconnect Wi-Fi briefly and watch reconnect behavior.

13. FAQ

14. Interview questions

15. Remember

• You can explain Enterprise Real-Time Systems in plain English.
• You have a runnable hub/SSE snippet to practice.
• You know a scale or security risk for this pattern.