VETRO

Integration pipeline pattern for hubs and iPaaS/ESB platforms.

Definition

VETRO separates a flow's concerns: Validate (reject malformed messages early), Enrich (add reference data from external sources), Transform (convert to/from the canonical model), Route (dispatch to the correct target) and Operate (invoke the target system). The ordering guarantees you validate and enrich before transforming and routing.

Origin

An integration-architecture pattern popularized by ESB/iPaaS platforms (notably MuleSoft documentation), building on the building blocks of Enterprise Integration Patterns (Hohpe & Woolf, 2003).

Example in context

An order flow: Validate the EDIFACT schema, Enrich the buyer GLN against the partner master, Transform to canonical, Route on company code, Operate by calling the ERP's API.

Related terms

• Canonical Data Model — the target of the Transform stage.
• Content-Based Router — the implementation of the Route stage.