> For the complete documentation index, see [llms.txt](https://www.opscompendium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opscompendium.com/dataops/data-pipelines.md).

# Data Pipelines

1. [Decision guide for data integration tools](https://www.metaplane.dev/blog/decision-guide-to-choosing-a-data-integration-tool)
2. [ETL vs ELT](https://www.qlik.com/us/etl/etl-vs-elt), [2](https://www.guru99.com/etl-vs-elt.html)
3. [What is reverse ETL (ELT)](https://torbjornzetterlund.com/what-is-reverse-etl/)?
4. [Airbyte](https://airbyte.com/) Open-source ELT data integration for modern data teams
5. [Stitch vs Airflow vs Rivery](https://www.stitchdata.com/vs/airflow/rivery/)
6. Rivery
7. Fivertran
   1. [Operators for AirFLow](https://www.fivetran.com/blog/announcing-the-fivetran-airflow-provider)
8. [Astronomer AirFlow as an orchestrator scheduler for FT, AB, etc](https://www.astronomer.io/blog/best-etl-tools-airflow/)
9. [The 7 Principles of reliable data pipelines](https://medium.com/bigeye/seven-principles-for-reliable-data-pipelines-e82a82810e4f) - bigeye medium article
10. [Hevo](https://hevodata.com/integrations/pipeline/) - Hevo is a Fully Automated, No-code Data Pipeline Platform that supports 150+ ready-to-use integrations across Databases, SaaS Applications, Cloud Storage, SDKs, and Streaming Services.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opscompendium.com/dataops/data-pipelines.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.