# Learn More

{% content-ref url="/pages/pD0nMCoibNNyguZMv5LF" %}
[Compliant LLM Gateway](/lisaiceland/platform+/subprocessors/compliant-llm-gateway.md)
{% endcontent-ref %}

> ### We use Docker Swarm as a native **container orchestration tool** that is integrated with the [Docker Engine](https://docs.docker.com/engine/swarm/) and allows developers and IT administrators to manage a cluster of Docker hosts as a single virtual system. 

This clustering capability, known as Swarm mode, provides features like high availability, fault tolerance, and automatic load balancing for containerized applications across multiple machines. 

## **Key Concepts:**

#### A Docker Swarm is comprised of the following key components:

* **Nodes** Physical or virtual machines running the Docker application that have joined the cluster. Nodes can function as either managers or workers.
  * **Manager Nodes** These nodes handle cluster management, orchestrate services, maintain the desired state of the system, and dispatch tasks to worker nodes. For high availability, it is recommended to have multiple manager nodes, typically three or five.
  * **Worker Nodes** These nodes receive and execute tasks assigned by the manager nodes.
* **Services and Tasks** A service defines the desired state of an application, such as the container image to use, the commands to run, and the number of replicas required. A task is a single instance of a container that runs on a worker node to fulfill the service definition.
* **Load Balancing** Swarm mode provides built-in, automatic load balancing to distribute incoming requests evenly across the running containers of a service.
* **Overlay Networking** Swarm automatically sets up an overlay network to facilitate communication between containers across different nodes in the cluster. 

#### Why Use Docker Swarm?

Docker Swarm offers several benefits, particularly for most deployment configurations: 

* **Simplicity** It is built directly into the Docker CLI and API, so users already familiar with Docker can easily transition to Swarm mode without learning an entirely new set of tools or a steep learning curve like with Kubernetes.
* **High Availability** The system uses a declarative model and desired state reconciliation, meaning if a node or container fails, the manager automatically creates a new one to replace it on an available, healthy node.
* **Rapid Deployment** It allows for quick setup and configuration, enabling teams to go from a single container setup to a scaled, clustered environment in minutes.
* **Security** Communication between nodes is secured by default using mutual Transport Layer Security (TLS) authentication and encryption. 

> ### For ease of use and rapid deployment for most of our PaaS workloads, Docker Swarm remains "the" solution for us. 


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://nexas-ridewiz.gitbook.io/lisaiceland/platform+/cloud-deploy/learn-more.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.