Recommendations to others considering JupyterHub:
Carefully consider which underlying technologies you'll use to run your sessions. Generally speaking, Docker and systemd are the easiest to set up and maintain, but they do not provide the same flexibility and elasticity you would get from Kubernetes and Mesos. Review collected by and hosted on G2.com.
What problems is JupyterHub solving and how is that benefiting you?
Before migrating to JupyterHub, we gave our researchers remote virtual machines to run computations required for their scientific work. This setup has serious drawbacks: it requires training in a specific toolset (SSH, Git, etc.), doesn't allow for dynamic resource allocation, and hinders our ability to change the underlying hardware without inflicting some downtime. When adopting a solution based on Jupyter Hub running on Apache Mesos, we can now abstract computing resources from machines and users, allowing for elastic cloud operations. Updating environments and changing hardware has now zero downtime, and our researchers don't need to learn a new toolset just to run their computations. Review collected by and hosted on G2.com.