

Building your pipeline or Using Airbyte
Airbyte is the only open source solution empowering data teams to meet all their growing custom business demands in the new AI era.
- Inconsistent and inaccurate data
- Laborious and expensive
- Brittle and inflexible
- Reliable and accurate
- Extensible and scalable for all your needs
- Deployed and governed your way
Start syncing with Airbyte in 3 easy steps within 10 minutes



Take a virtual tour
Demo video of Airbyte Cloud
Demo video of AI Connector Builder
What sets Airbyte Apart
Modern GenAI Workflows
Move Large Volumes, Fast
An Extensible Open-Source Standard
Full Control & Security
Fully Featured & Integrated
Enterprise Support with SLAs
What our users say


"The intake layer of Datadog’s self-serve analytics platform is largely built on Airbyte.Airbyte’s ease of use and extensibility allowed any team in the company to push their data into the platform - without assistance from the data team!"


“Airbyte helped us accelerate our progress by years, compared to our competitors. We don’t need to worry about connectors and focus on creating value for our users instead of building infrastructure. That’s priceless. The time and energy saved allows us to disrupt and grow faster.”


“We chose Airbyte for its ease of use, its pricing scalability and its absence of vendor lock-in. Having a lean team makes them our top criteria. The value of being able to scale and execute at a high level by maximizing resources is immense”
1. Install the Google Cloud SDK if you haven't already, and authenticate to your GCP account using `gcloud auth login`.
2. Install Apache Hadoop and Apache Spark. Ensure that they are properly configured to work together.
3. Add Apache Iceberg libraries to your Spark environment. You can do this by including the Iceberg dependency in your build file or by submitting Spark jobs with the Iceberg JARs.
Use the Google Cloud SDK to download the data from your GCS bucket to your local machine or server. You can use the `gsutil cp` command to copy files from GCS. For example:gsutil cp gs://your-bucket-name/path/to/data/* /local/path/to/store/data/
1. Add Iceberg tables to your Hive catalog or use Hadoop Tables if you prefer not to use Hive.
2. Initialize the Iceberg table using Spark or directly through the Iceberg API. For example, using Spark: val spark = SparkSession.builder()
.appName("Iceberg")
.config("spark.sql.catalog.local", "org.apache.iceberg.spark.SparkCatalog")
.config("spark.sql.catalog.local.type", "hadoop")
.config("spark.sql.catalog.local.warehouse", "hdfs:///path/to/iceberg/warehouse")
.getOrCreate()
spark.sql("CREATE TABLE local.db.table_name (id bigint, data string) USING iceberg")
1. Using Spark, read the data that was downloaded from GCS into a DataFrame. For example:val df = spark.read.format("json").load("/local/path/to/store/data/") // Use the appropriate format for your data
2. Write the DataFrame to the Iceberg table:df.write.format("iceberg").mode("append").save("local.db.table_name")
Once the data has been written to the Iceberg table, you can perform a read operation to verify that the transfer was successful:val results = spark.read.format("iceberg").load("local.db.table_name")
results.show()
After verifying the data transfer, you can remove the local copies of the data that were downloaded from GCS to free up space.
1. The above steps are suitable for a one-time transfer or proof of concept. For production use, you may want to automate the process using Apache Airflow, Apache NiFi, or another workflow management tool.
2. Consider implementing monitoring, logging, and alerting to keep track of the data transfer process and quickly identify any issues.
3. Ensure that your data transfer adheres to your organization's data governance and compliance policies.
FAQs
What is ETL?
ETL, an acronym for Extract, Transform, Load, is a vital data integration process. It involves extracting data from diverse sources, transforming it into a usable format, and loading it into a database, data warehouse or data lake. This process enables meaningful data analysis, enhancing business intelligence.
Google Cloud Storage is a cloud-based storage service that allows users to store and access their data from anywhere in the world. It provides a highly scalable and durable storage solution for businesses and individuals, with features such as automatic data replication, versioning, and access control. Google Cloud Storage offers different storage classes to suit different needs, including multi-regional, regional, nearline, and coldline storage. It also integrates with other Google Cloud services, such as BigQuery and Cloud Functions, to enable data analysis and processing. Overall, Google Cloud Storage provides a reliable and flexible storage solution for businesses of all sizes.
Google Cloud Storage's API provides access to various types of data, including:
1. Object data: This includes files and other data objects stored in Google Cloud Storage buckets.
2. Metadata: This includes information about the objects stored in the buckets, such as their size, creation date, and content type.
3. Access control data: This includes information about who has access to the objects stored in the buckets and what level of access they have.
4. Bucket data: This includes information about the buckets themselves, such as their name, location, and storage class.
5. Logging data: This includes information about the activity in the buckets, such as who accessed them and when.
6. Transfer data: This includes information about data transfers to and from the buckets, such as the amount of data transferred and the transfer speed.
Overall, the Google Cloud Storage API provides access to a wide range of data related to object storage and management in the cloud.
What is ELT?
ELT, standing for Extract, Load, Transform, is a modern take on the traditional ETL data integration process. In ELT, data is first extracted from various sources, loaded directly into a data warehouse, and then transformed. This approach enhances data processing speed, analytical flexibility and autonomy.
Difference between ETL and ELT?
ETL and ELT are critical data integration strategies with key differences. ETL (Extract, Transform, Load) transforms data before loading, ideal for structured data. In contrast, ELT (Extract, Load, Transform) loads data before transformation, perfect for processing large, diverse data sets in modern data warehouses. ELT is becoming the new standard as it offers a lot more flexibility and autonomy to data analysts.
What should you do next?
Hope you enjoyed the reading. Here are the 3 ways we can help you in your data journey: