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.
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.