Deploy an R Shiny app called "Box Office Mojo" courtesy of.After doing it several times now, I wanted to share the website that I thought provided the best walk-through as well as offer some of my tips. There are multiple blogs online that provide great, detailed instructions on how to do this. Shiny-server Pro: (paid) allows you to optimize between CPU and memory, provides authentication, user monitoring, etc., but includes a subscription cost.Īctually measuring/testing app scalability: Use shiny load test (see for more details).For a recent company project, I helped deploy an R Shiny app developed by a teammate to AWS. In ShinyProxy, each user will get their own Docker container/app which could be distributed between multiple processors, supporting better scaling of compute-heavy apps.Īuthentication: Authentication only supported by ShinyProxy (or Shiny-server Pro) So many concurrent users may experience a slowdown of a compute-heavy app when hosted using Shiny-server. Many instances of an app that demands a lot of memory will drain your server resources faster if it is hosted using ShinyProxy vs Shiny-server.ĬPU: Multiple instances of the same app will share the same R instance and processor thread in Shiny-server. Memory: Shiny-server can share memory between multiple instances of the same app while each instance of a ShinyProxy app is completely independent. The most cost-efficient option will be the first option in this list that meets all of your needs: (1) shinyapps.io, (2) shiny-server (free), (3) ShinyProxy, (4) Shiny-server Pro.
ShinyProxy: takes even longer to setup, requires a server, experience with Docker, very capable.shiny-server: takes longer to setup, requires a server, but fewer limitations.shinyapps.io: by far the cheapest, so long as it meets your needs.I have hosted apps using the three approaches listed in the table.
0 kommentar(er)
