Using OSS (SignalR, React) to Connect Users to an API in NRT (Near-Real Time)
summary
A WebSocket pipeline using SignalR (WebSockets) and a React UI relays Avaya agent desktop events to specific browser tabs, pre-populates patient demographics, and avoids blocking the critical path when a backend patient-lookup API takes anywhere from ~1–5 seconds to occasionally ~60 seconds. External integrations live in a separate integration engine microservice so the core app stays responsive. Deployed on Azure SignalR managed (10k scale), it increases complexity but works in production and simplifies agent workflows.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:51Call center workflows
- 3:59Desktop-web integration challenges
- 6:28SignalR for real-time routing
- 8:57SignalR over alternatives
- 12:28Integration engine
- 17:02SignalR targeting and edge cases
- 21:34Q&A
- 25:30OSS reliance and community
related talks
33mRealtime web applications, from your Mac to the Cloud, with SignalR and Azure
44mGoing real time using Azure CosmosDB and React
43mGetting real(time) with Akka.NET, React and Redux
53mSignalR: To Chat and Beyond
01h 01mEvent driven applications in Azure
43mRealtime Web Apps in the Wild
45mKeeping it Real(time)
31mGoing real time using Azure CosmosDB and React
