https://jupyter-server.readthedocs.io/en/latest/
5b5ca0b8-cad5-4413-8479-208fe053b179-image.png
Jupyter Server contains the following components:
ServerApp is the main Tornado-based application which connects all components together.
Config Manager initializes configuration for the ServerApp. You can define custom classes for the Jupyter Server managers using this config and change SererApp settings. Follow the Config File Guide to learn about configuration settings and how to build custom config.
Custom Extensions allow you to create the custom Server’s REST API endpoints. Follow the Extension Guide to know more about extending ServerApp with extra request handlers.
Gateway Server is a web server that, when configured, provides access to Jupyter kernels running on other hosts. There are different ways to create a gateway server. If your ServerApp needs to communicate with remote kernels residing within resource-managed clusters, you can use Enterprise Gateway, otherwise, you can use Kernel Gateway, where kernels run locally to the gateway server.
Contents Manager and File Contents Manager are responsible for serving Notebook on the file system. Session Manager uses Contents Manager to receive kernel path. Follow the Contents API guide to learn about Contents Manager.
Session Manager processes users’ Sessions. When a user starts a new kernel, Session Manager starts a process to provision kernel for the user and generates a new Session ID. Each opened Notebook has a separate Session, but different Notebook kernels can use the same Session. That is useful if the user wants to share data across various opened Notebooks. Session Manager uses SQLite3 database to store the Session information. The database is stored in memory by default, but can be configured to save to disk.
Mapping Kernel Manager is responsible for managing the lifecycles of the kernels running within the ServerApp. It starts a new kernel for a user’s Session and facilitates interrupt, restart, and shutdown operations against the kernel.
Jupyter Client library is used by Jupyter Server to work with the Notebook kernels.
Kernel Manager manages a single kernel for the Notebook. To know more about Kernel Manager, follow the Jupyter Client APIs documentation.
Kernel Spec Manager parses files with JSON specification for a kernels, and provides a list of available kernel configurations. To learn about Kernel Spec Manager, check the Jupyter Client guide.
0c508af6-fbf0-4f42-b0fb-a4468da9cdc2-image.png
https://jupyter-server.readthedocs.io/en/latest/developers/rest-api.html
https://jupyter-server.readthedocs.io/en/latest/operators/multiple-extensions.html
One of the major benefits of Jupyter Server is that you can run serve multiple Jupyter frontend applications above the same Tornado web server. That’s because every Jupyter frontend application is now a server extension. When you run a Jupyter Server with multiple extensions enabled, each extension appends its own set of handlers and static assets to the server.