~/talk

Using OSS (SignalR, React) to Connect Users to an API in NRT (Near-Real Time)

links:none on file
slides:none on file

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

  1. 0:00Introduction
  2. 1:51Call center workflows
  3. 3:59Desktop-web integration challenges
  4. 6:28SignalR for real-time routing
  5. 8:57SignalR over alternatives
  6. 12:28Integration engine
  7. 17:02SignalR targeting and edge cases
  8. 21:34Q&A
  9. 25:30OSS reliance and community
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.