

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


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


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

"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 your Kafka environment is up and running. This includes having your Kafka broker and Zookeeper properly configured. Verify that your Kafka topic is set up to receive the data you intend to stream. You can use the Kafka command-line tools to create and manage topics and to check the status of your Kafka cluster.
Access your Databricks account and create a new cluster if you haven't already. Ensure that your cluster has the necessary resources and configurations to handle streaming data. You will also need to have a workspace set up in Databricks where you can write and execute your code.
In your Databricks environment, install the Apache Spark Kafka integration library. This is typically included in Databricks by default, but you should verify its availability. If not present, you can install it via the Databricks library interface using Maven coordinates, for example: `org.apache.spark:spark-sql-kafka-0-10_2.12:`.
Open a new notebook in Databricks. Use the Spark Kafka integration to configure Kafka as a source. You can create a streaming DataFrame by specifying the Kafka server, the topic you want to subscribe to, and any other necessary Kafka configurations such as starting offsets and security protocol if your Kafka setup requires authentication.
```python
kafka_data_df = (spark
.readStream
.format("kafka")
.option("kafka.bootstrap.servers", ":")
.option("subscribe", "")
.load())
```
Once you have the streaming DataFrame, process it as needed. This might involve parsing the data from its serialized form, applying transformations, or filtering. Use Spark SQL or DataFrame operations to handle this processing. For example, if your data is in JSON format, you can use the `from_json` function to parse it.
```python
from pyspark.sql.functions import from_json, col
from pyspark.sql.types import StructType, StringType
schema = StructType().add("field1", StringType()).add("field2", StringType())
processed_df = kafka_data_df.selectExpr("CAST(value AS STRING)") \
.select(from_json(col("value"), schema).alias("data")) \
.select("data.")
```
Configure the output sink to write the processed data to Databricks Lakehouse. This is typically done by writing the stream to a Delta table. Specify the output mode (e.g., append), the location or Delta table name, and any checkpointing details needed for fault tolerance.
```python
query = (processed_df
.writeStream
.format("delta")
.outputMode("append")
.option("checkpointLocation", "/path/to/checkpoint/dir")
.start("/mnt/delta/your-delta-table"))
```
Once your streaming job is running, monitor it using the Databricks job interface. Check for any errors or performance issues and adjust resource allocation or code optimizations as necessary. Use the streaming metrics and logs available in Databricks to debug and enhance your data pipeline.
By following these steps, you can efficiently move data from Kafka to your Databricks Lakehouse using only the built-in capabilities of Kafka and Databricks.
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.
Apache Kafka is an open-source distributed event streaming platform that is used to handle real-time data feeds. It is designed to handle high volumes of data and provide real-time processing and analysis of data streams. Kafka is used by many companies for various purposes such as data integration, real-time analytics, and messaging. It is highly scalable and fault-tolerant, making it a popular choice for large-scale data processing. Kafka provides a publish-subscribe model where producers publish data to topics, and consumers subscribe to those topics to receive the data. It also provides features such as data retention, replication, and partitioning to ensure data reliability and availability.
Kafka's API gives access to various types of data, including:
1. Event data: Kafka is primarily used for streaming event data, such as user actions, sensor readings, and log data.
2. Metadata: Kafka provides metadata about the topics, partitions, and brokers in a cluster.
3. Consumer offsets: Kafka tracks the offset of each message consumed by a consumer, allowing for reliable message delivery.
4. Producer metrics: Kafka provides metrics on the performance of producers, such as message send rate and error rate.
5. Consumer metrics: Kafka provides metrics on the performance of consumers, such as message consumption rate and lag.
6. Log data: Kafka stores log data for a configurable amount of time, allowing for historical analysis and debugging.
7. Administrative data: Kafka provides APIs for managing topics, partitions, and consumer groups.
Overall, Kafka's API gives access to a wide range of data related to event streaming, metadata, performance metrics, and administrative tasks.
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: