Dataflows for complex use cases:
Implementing an event-driven end-to-end data pipeline can be challenging — raw webhooks from third-party vendors like Stripe or GitHub are typically verbose and unwieldy for analytics. To simplify downstream processing, we split the pipeline into two distinct stages:
Converts raw vendor events into compact, Fluvio-native types.
- Example: stripe-reduce
Consumes those reduced types and executes one or more domain-specific transformations or actions.
- Example: stripe-slack
You can chain as many Process pipelines as your use cases require — each one targets a specific analytic, notification, or enrichment task.