Summarize


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
Setup Complexities simplified!
Simple & Easy to use Interface
Airbyte is built to get out of your way. Our clean, modern interface walks you through setup, so you can go from zero to sync in minutes—without deep technical expertise.
Guided Tour: Assisting you in building connections
Whether you’re setting up your first connection or managing complex syncs, Airbyte’s UI and documentation help you move with confidence. No guesswork. Just clarity.
Airbyte AI Assistant that will act as your sidekick in building your data pipelines in Minutes
Airbyte’s built-in assistant helps you choose sources, set destinations, and configure syncs quickly. It’s like having a data engineer on call—without the overhead.
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

Andre Exner

"For TUI Musement, Airbyte cut development time in half and enabled dynamic customer experiences."

Chase Zieman

“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.”

Rupak Patel
"With Airbyte, we could just push a few buttons, allow API access, and bring all the data into Google BigQuery. By blending all the different marketing data sources, we can gain valuable insights."
Begin by ensuring that you have an active Azure Storage account. Within this account, create a Blob Container where your data files are stored. Note the container name, storage account name, and the corresponding access keys since these will be necessary for establishing a connection later.
Create an Azure Service Principal to facilitate secure access to your Blob Storage. This involves registering an application in Azure Active Directory, generating a client secret, and granting the necessary permissions to the storage account. Record the client ID, tenant ID, and client secret for future use.
Access your Databricks workspace and ensure it is properly configured. Create a new cluster if you don’t have one already, and ensure that it has appropriate permissions to access Azure resources.
In a Databricks notebook, use the Azure Service Principal credentials to mount the Blob Storage. This can be accomplished using the Databricks File System (DBFS) utility. Implement the following `dbutils.fs.mount` command, substituting with your actual configuration values:
```python
configs = {
"fs.azure.account.auth.type": "OAuth",
"fs.azure.account.oauth.provider.type": "org.apache.hadoop.fs.azurebfs.oauth2.ClientCredsTokenProvider",
"fs.azure.account.oauth2.client.id": "",
"fs.azure.account.oauth2.client.secret": "",
"fs.azure.account.oauth2.client.endpoint": "https://login.microsoftonline.com//oauth2/token"
}
dbutils.fs.mount(
source = "abfss://@.dfs.core.windows.net/",
mount_point = "/mnt/",
extra_configs = configs)
```
Once mounted, verify the connection by listing the files in the mounted directory. Use the following command in your Databricks notebook:
```python
display(dbutils.fs.ls("/mnt/"))
```
This command should display the contents of your Azure Blob Storage, confirming successful access.
Use Apache Spark's DataFrame API to read the data from the mounted Blob Storage into Databricks. Here’s an example of reading a CSV file:
```python
df = spark.read.format("csv").option("header", "true").load("/mnt//path/to/yourfile.csv")
df.show()
```
Adjust the format and options based on your data file type (e.g., JSON, Parquet).
Finally, write the DataFrame to your desired format in the Databricks Lakehouse. For example, to write as a Delta table:
```python
df.write.format("delta").mode("overwrite").save("/mnt/lakehouse/your-delta-table")
```
This operation will save the data into Databricks Lakehouse in the Delta format, making it ready for further processing or analysis.
By following these steps, you can seamlessly transfer data from Azure Blob Storage to Databricks Lakehouse using built-in capabilities, without relying on third-party connectors or integrations.
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.
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: