> For the complete documentation index, see [llms.txt](https://docs.arcology.network/streamer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcology.network/streamer/special-actors/pipeliner.md).

# Pipeliner

The Pipeliner actor is a specialized actor responsible for serializing a sequence of individual actors. This scenario commonly occurs when multiple actors collaborate in a sequential manner to process events. In this process, each actor generates some output events, which are then processed by the subsequent actor, creating a chain-like flow. The sequencer serves as a mechanism to bind these actions together, ensuring that the processing occurs in a specific serial order.

The decision to use multiple actors with a sequencer is often driven by the requirements of the system.

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

### Single Actor vs Pipeliner

There are some advantages to connecting multiple actors together with a Pipeliner instead of combining them into a single actor.

* **Modularity:** It's often easier to modify or extend a specific actor rather than modifying a monolithic actor that does everything. If a specific processing step needs to be replaced or modified, it can be done without affecting others.
* **Deployment Independence:** In a distributed deployment setup, different actors may be deployed on various machines; therefore, it isn't always possible to combine multiple actors into a single one.