This document describes the architecture of the services that are parts of the Renku platform.
The Renku platform consists of several off-the-shelf components from the software engineering and data science software stacks, as well as customized or newly developed services. The services communicate among each other through REST APIs. The deployment is orchestrated on Kubernetes through the use of Helm charts. Because of its micro-service architecture, Renku is by definition modular, and therefore able to accommodate other languages or implementations used for individual components.
Renku has the following custom components:
- renku: the meta repository with deployment scripts, documentation and kubernetes helm charts
renku-gateway <api_gateway>: an API gateway connecting clients to the APIs of the different backend servicesrenku-graph <graph_services>: a collection of services concerned with activating, building and querying the Renku knowledge graphrenku-notebooks <notebooks_service>: a service integrating GitLab repositories with JupyterHub- renku-python: python API & Command Line Interface (CLI)
- renku-ui: web front-end interface
In addition, we make use of:
- JupyterHub: management of interactive notebook servers
- GitLab: repository management, CI and various related APIs
- Keycloak: identity management and user authentication
The figure below shows an overview of the components and their interactions. Blue components are off-the-shelf, yellow components are either built or extended by us.
/_static/graphviz/renku_architecture.dot