Skip to content

Architecture⚓︎

The Application Hub combines the power of Kubernetes and JupyterHub to offer a scalable, resilient, and user-centric platform for Earth Observation applications and analyses. Kubernetes, which serves as its orchestration layer ensures scalable, manageable, and efficient operation of containerized applications:

  • Pod Structure: Every application in the Hub is run within a Kubernetes pod. This structure guarantees isolation, security, and the ability to scale each application independently based on demand.
  • Service Exposure: Upon being deployed and reaching an operational state, these pods expose their services, making them accessible via specific ports. This architecture allows users to interact with the applications through standard web browsers, minimizing the need for specialized tools or software on the client side.
  • Load Balancing and Networking: Using Kubernetes, the Application Hub can automatically distribute incoming application traffic across multiple pods, ensuring high availability and fault tolerance. Moreover, Kubernetes provides intricate networking capabilities, enabling smooth communication between pods and external services.

Central to the Application Hub’s operation is JupyterHub, which orchestrates the launching, scaling, and management of software deployments. While it naturally supports applications like JupyterLab or the IDE Code Server, it also showcases its versatility by functioning as a Software-as-a-Service (SaaS) solution for remote desktop applications, notably QGIS and SNAP, and facilitates the seamless integration and presentation of various dashboards. JupyterHub dynamically provisions the right environment for users and acts as the primary gateway, channeling user requests to the respective application pods, ensuring efficient resource utilization and streamlined user access.

The Application Hub leverages the dynamic capabilities of Kubernetes and JupyterHub to provide personalized and context-aware application experiences:

  • Namespaces: By deploying each application pod in its dedicated namespace, the Hub ensures an organized, secure, and isolated environment. This setup also facilitates easy management, monitoring, and logging of individual application instances.
  • Application Contextualization: This involves dynamically setting up the application pod based on the task at hand. It ensures that the pod has all necessary configurations, from environment variables to specific files (like S3 or Docker configurations), ensuring the application runs optimally.
  • User Profile Management with Kube Spawner: The kube spawner plays a crucial role in contextualizing the application pod experience based on user profiles. From managing authentication and authorization protocols to handling lifecycle events with pre-spawn and post-stop hooks, it ensures a seamless user experience.

This architectural design ensures that the Application Hub remains modular, scalable, and capable of catering to the dynamic and ever-evolving requirements of Earth Observation tasks.