> 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/technical-details.md). # Technical Details ## Worker Processes are Isolated When you run a Blueprint cluster, each worker processes is isolated from its peers and from the parent process. This means that each worker process has its own copy of the Blueprint application. Moreover, it means that each worker process cannot directly access the state of its peers. It is important to note this fact because it is easy to misunderstand why two worker processes are experiencing unexpected behavior—especially if your Blueprint application is stateful. ## Communicating Between Master and Worker Process It is possible to communicate between the master and worker processes. At the moment, Blueprint cluster does not have native abstractions for supporting such communication needs. If you need to communicate between the master and worker process, then you have to rely on the abstractions from the [native NodeJS cluster module](https://nodejs.org/api/cluster.html). --- # 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/technical-details.md?ask=&goal= ``` `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.