Closed bevingtona closed 8 months ago
in the meantime... could spin up different endpoints for different teams... even password protect a few for critical work. Seems it is a shinyapps.io scalling problem, not a database problem.
For example [url]/watershedBC_RESEARCH For example [url]/watershedBC_AUTHORIZATION For example [url]/watershedBC_DRINKING_WATER
swapped the DBI lib to pool, seems stable
Not currently built for production... Slows down with too many concurrent users.
Need to load test and benchmark performance.
https://github.com/hadley/mastering-shiny/blob/master/scaling-performance.Rmd
Then potentially move some computation to JavaScript and use
shinyworkers
to distribute computation...