Domino services are best understood when arranged into logical layers based on function and communication. This topic describes the functionality provided by each layer.
The client layer contains the frontend pods that are the targets of a network load balancer. The frontends run on platform nodes. To access Domino’s core features, Domino users connect to the frontends through one of the following:
Web browser: The frontend serves the Domino application.
HTTPS request to the Domino API: The frontend routes to the API server.
Domino CLI: Uses the API.
The service layer contains the Domino API server, Dispatcher, Keycloak authentication service, and the metadata services that Domino uses to provide reproducibility and collaboration features.
MongoDB stores application object metadata, Git manages code and file versioning, Elasticsearch powers in-app search, and the Docker registry is used by Domino Environments. Project data, logs, and backups are written to durable blob storage.
All these services run on platform nodes.
The service layer also contains the dedicated master nodes for the Kubernetes cluster.