Pipe and Filter Design Pattern

Break up logic in small steps instead of a long-run service or process.

Approach

  • Each request must call services separately instead of a long-running service.
  • Data is passed from one filter to another filter.
  • Filters exchange data use a standardized format and protocol.

Why filter data must be standardized?

  • We can add or remove filters to/from pipeline.
  • Reorder filter execution.
  • Use the same filter in different pipelines.

Published by parisamoosavinezhad

- Software Engineer - Software Architect - Software and database specialist - Cloud solution architect

2 thoughts on “Pipe and Filter Design Pattern

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: