League\Pipeline
This package provides a pipeline pattern implementation.
Pipeline Pattern
The pipeline pattern allows you to easily compose sequential stages by chaining stages.
In this particular implementation the interface consists of two parts:
- StageInterface
- PipelineInterface
A pipeline consists of zero, one, or multiple stages. A pipeline can process a payload. During the processing the payload will be passed to the first stage. From that moment on the resulting value is passed on from stage to stage.
In the simplest form, the execution chain can be represented as a foreach:
$result = $payload;
foreach ($stages as $stage) {
$result = $stage($result);
}
return $result;
Effectively this is the same as:
$result = $stage3($stage2($stage1($payload)));
Immutability
Pipelines are implemented as immutable stage chains. When you pipe a new stage, a new pipeline will be created with the added stage. This makes pipelines easy to reuse, and minimizes side-effects.
Usage
Operations in a pipeline, stages, can be anything that satisfies the callable type-hint. So closures and anything that's invokable is good.
$pipeline = (new Pipeline)->pipe(function ($payload) {
return $payload * 10;
});
Class based stages.
Class based stages are also possible. The StageInterface can be implemented which ensures you have the correct method signature for the __invoke method.
use League\Pipeline\Pipeline;
use League\Pipeline\StageInterface;
class TimesTwoStage implements StageInterface
{
public function __invoke($payload)
{
return $payload * 2;
}
}
class AddOneStage implements StageInterface
{
public function __invoke($payload)
{
return $payload + 1;
}
}
$pipeline = (new Pipeline)
->pipe(new TimesTwoStage)
->pipe(new AddOneStage);
// Returns 21
$pipeline->process(10);
Re-usable Pipelines
Because the PipelineInterface is an extension of the StageInterface pipelines can be re-used as stages. This creates a highly composable model to create complex execution patterns while keeping the cognitive load low.
For example, if we'd want to compose a pipeline to process API calls, we'd create something along these lines:
$processApiRequest = (new Pipeline)
->pipe(new ExecuteHttpRequest) // 2
->pipe(new ParseJsonResponse); // 3
$pipeline = (new Pipeline)
->pipe(new ConvertToPsr7Request) // 1
->pipe($processApiRequest) // (2,3)
->pipe(new ConvertToResponseDto); // 4
$pipeline->process(new DeleteBlogPost($postId));
Pipeline Builders
Because pipelines themselves are immutable, pipeline builders are introduced to facilitate distributed composition of a pipeline.
The pipeline builders collect stages and allow you to create a pipeline at any given time.
use League\Pipeline\PipelineBuilder;
// Prepare the builder
$pipelineBuilder = (new PipelineBuilder)
->add(new LogicalStage)
->add(new AnotherStage)
->add(new LastStage);
// Build the pipeline
$pipeline = $pipelineBuilder->build();
Exception handling
This package is completely transparent when dealing with exceptions. In no case will this package catch an exception or silence an error. Exceptions should be dealt with on a per-case basis. Either inside a stage or at the time the pipeline processes a payload.
$pipeline = (new Pipeline)->pipe(function () {
throw new LogicException();
});
try {
$pipeline->process($payload);
} catch(LogicException $e) {
// Handle the exception.
}
![[Feature Request] Fork-Join](https://avatars.githubusercontent.com/u/1373803?v=4)
![[Feature Request] Attach a listener to a pipeline](https://avatars.githubusercontent.com/u/11049718?v=4)
![[Feature Request] Lazily retrieve pipeline stages from PSR-11 container](https://avatars.githubusercontent.com/u/954385?v=4)
