> For the complete documentation index, see [llms.txt](https://blueprint.onehilltech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blueprint.onehilltech.com/developer-guide/blueprint-cluster/background.md).

# What is a Blueprint Cluster?

[Clustering](https://nodejs.org/api/cluster.html) in NodeJS is the process of running multiple instances of a NodeJS application such that one process is the master process and the other processes are worker processes. This is necessary feature because a NodeJS application is single-threaded. This means that all events are processed by the same execution thread. We you run a NodeJS application on a multi-core machine, it is hard for the NodeJS application to take advantage of computing power available via the many cores on the machine.

We understand the importance of [running a NodeJS cluster](https://nodejs.org/api/cluster.html) when it relates to scaling an NodeJS application to handle large numbers of requests. We therefore have integrated cluster support into Blueprint.

{% hint style="info" %}
A *Blueprint cluster* is when you run a Blueprint application as a NodeJS cluster.
{% endhint %}

{% hint style="info" %}
Blueprint cluster is an experimental feature. Its functionality may change in the future as we learn more about its usage in the wild.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://blueprint.onehilltech.com/developer-guide/blueprint-cluster/background.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.