Real Time Shiny Applications
summary
Prototype sends R objects (ggplot2 plots) from remote jobs into a Shiny UI using WebSockets, then persists and shares them with multiple viewers by writing to rethink DB. First version delivers plots to only the most recent session; after forking shiny doc collections to use rethink DB, multiple clients see the same state and closed tabs restore content. Remaining issues: socket server and Shiny must run in the same R process for auto-updates to work, and endpoint routing is still experimental.
AI-written summary · about
chapters (13)
- 0:00Start
- 4:52Data in Shiny Apps
- 5:12Updating data in a shiny app
- 7:55Old fashioned
- 10:00What do we want?
- 10:53Hacky solution
- 12:15Hands up
- 13:03Websockets
- 13:50Version 0.1
- 18:07Rethink
- 18:58shiny.collection
- 23:38Issues
- 24:26What to do next
related talks
18mShiny New Tools for Scaling your Shiny Apps
19mThe future's Shiny: Pioneering genomic medicine in R
04mSpeeding Up Plots in R/Shiny
18mWait, that’s Shiny? Building feature-full, user-friendly interactive data explorers
24mRSCs In Production: 1 Year Later
32mAchieving Concurrency in Streamlit with a RQ scheduler
47mReact, Rendering, Performance
29mHigh Performance Data Visualization for the Web