# Run concepts

## Deployment

Deployment refers to the process of activating pipelines that have already been configured with a trigger. This activation can happen in either test or production. If you want to learn more about how to deploy a pipeline, read the [documentation](/documentation/developer-guide/development-cycle/overview/deployment/deployments.md).<br>

The deployment has three related concepts:&#x20;

### Pipeline size

The pipeline deployment size depends on the processing capacity and memory of each replica. There are three sizes for deployments:

<figure><img src="/files/urQxKtKKAXqRLpcBLGEX" alt=""><figcaption></figcaption></figure>

* SMALL, 10 consumers, 20% of 1 CPU, 64 MB memory&#x20;
* MEDIUM, 20 consumers, 40% of 1 CPU, 128 MB memory&#x20;
* LARGE, 40 consumers, 80% of 1 CPU, 256 MB memory

For example, if you configure a SMALL deployment size for your pipeline executions, it means that 10 messages can be concurrently processed.

### Concurrent executions

Concurrent executions represent the number of executions each deployed replica can run at the same time. The maximum number of concurrent executions depends on the deployment size configured.

<figure><img src="/files/ybsUB0nX228kemZCq4Xs" alt=""><figcaption></figcaption></figure>

Learn more about these concepts in the [Pipeline Engine documentation](/documentation/developer-guide/development-cycle/overview/runtime/pipeline-engine.md).&#x20;

### Replicas

Choosing the adequate number of replicas will support your integrations with high availability, guaranteeing their autonomy and the efficiency of their concurrent executions.&#x20;

<figure><img src="/files/FeoREEW0TCp8bin53ygt" alt=""><figcaption></figcaption></figure>


---

# 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://docs.digibee.com/documentation/developer-guide/development-cycle/overview/runtime.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.