Airbyte5 min read
Airbyte in Production: A Successful Sync of Zero Rows Is Still an Outage
Green sync, empty destination, raw JSON versus typed silver, self-host versus Cloud, and why Airbyte does not replace dbt.
- airbyte
- elt
All stacks · Ingestion & ELT
Airbyte
Open-source ELT connectors into warehouses and lakes.
AirbyteAbout Airbyte
Airbyte is the open-source ELT connector platform: extract from SaaS and databases, load into warehouses and lakes, optionally transform later in dbt. You operate the workers; you do not write a new Python extractor for every vendor.
The production work is connector reliability, schema change, and not treating “the sync succeeded” as “the grain is correct.”
What you'll learn here
- Sources, destinations, and normalization vs raw JSON
- Self-hosted vs Cloud and who pages when a connector breaks
- Schema drift and why you version the raw layer
- Airbyte vs Fivetran vs Debezium — pick by source type, not branding
Frequently asked questions
Airbyte or Fivetran?
Fivetran if you want a vendor SLA and usage-based pricing you can explain to finance. Airbyte if you want open connectors, self-host, or sources Fivetran prices badly. Many teams run Airbyte for a few sources and Fivetran for the rest.
Does Airbyte replace dbt?
No. Load raw, then model. Normalization helpers are not a mart layer. Grain and tests still belong in dbt or SQLMesh.
Why is the destination a mess of JSON?
You loaded raw without a typed silver layer. That is correct for day one and wrong as the serving layer. Keep raw, parse in transform.
New Airbyte posts, straight to your inbox
One email a week with our latest tutorials. No spam.
Newsletter signup is not live yet. Use the contact form if you want to be notified.