General

A pipeline is the flow of data from one or more producing systems to one or more consuming systems on a single canvas.

Considerations

Considerations for separating pipelines:

• Operability - Minimise impact on operations during changes + contain impact to operations if multiple sites are involved and there's an operational issue
• Maintainability - Particularly when there's multiple sites involved, perhaps with different applications or different versions of applications (or even just different endpoints), reduces the amount of special cases required in the overall pipeline. Avoiding a design that looks like spaghetti helps to improve maintainability.
• Supportability - how does Solution Support work? One team that looks after everything? Individual sites with individual teams? One site that has lower reliability?
• Connectivity - Pipelines have some isolation from each other at a network layer. If bringing multiple sites together, is that ok given your intended network architecture.
• Scalability - Each pipeline will have a certain natural capacity, associated with the workload implied by the plugins involved and the vertical and horizontal scaling characteristics of the platform instance involved.
• Cost - What's the pricing model of your Reekoh subscription?