

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."
Start by connecting to your MySQL database using a tool like the MySQL command line client or MySQL Workbench. Use SQL `SELECT` queries to extract the data you need. Export the data to a CSV file or any other format that is easy to process programmatically. Ensure that the data is clean and free of errors to avoid complications in the later steps.
Log into your AWS Management Console and navigate to DynamoDB. If you haven't already, create a new DynamoDB table that matches the schema of your MySQL data. Define the primary key, sort key (if needed), and any local or global secondary indexes based on how you plan to access the data in DynamoDB.
Convert your MySQL data into a format compatible with DynamoDB. This typically means transforming your data into JSON objects that match the attribute types in your DynamoDB table. You can write a script in a language like Python or JavaScript to automate this conversion. Pay attention to attribute types in DynamoDB, such as String, Number, Binary, etc.
Use AWS SDKs (such as Boto3 for Python or AWS SDK for JavaScript) to write the data to DynamoDB. The SDKs provide methods to perform batch writes, which is efficient for inserting large volumes of data. Break down your data into chunks of 25 items or less, as DynamoDB's `BatchWriteItem` API has a limit of 25 items per request.
DynamoDB has provisioned capacity limits, and exceeding these can cause throttling. Monitor your write throughput and adjust the provisioned capacity of your DynamoDB table as necessary. Alternatively, you can enable on-demand capacity mode, which automatically scales to accommodate your workload.
Once the data is loaded, run queries to verify that the data in DynamoDB matches what was in MySQL. Check for any discrepancies or missing records. You can use the AWS Management Console or scripts using AWS SDKs to query and validate the data.
After migration, optimize your DynamoDB table settings for your expected workload. This might include setting up auto-scaling policies for capacity, enabling DynamoDB Streams if you need to keep track of changes, and configuring CloudWatch alarms for monitoring performance and throughput usage. Regularly monitor your table to ensure it operates efficiently and cost-effectively.
Following these steps will help you successfully move your data from MySQL to DynamoDB without relying on third-party tools.
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.
MySQL is an SQL (Structured Query Language)-based open-source database management system. An application with many uses, it offers a variety of products, from free MySQL downloads of the most recent iteration to support packages with full service support at the enterprise level. The MySQL server, while most often used as a web database, also supports e-commerce and data warehousing applications and more.
MySQL provides access to a wide range of data types, including:
1. Numeric data types: These include integers, decimals, and floating-point numbers.
2. String data types: These include character strings, binary strings, and text strings.
3. Date and time data types: These include date, time, datetime, and timestamp.
4. Boolean data types: These include true/false or yes/no values.
5. Spatial data types: These include points, lines, polygons, and other geometric shapes.
6. Large object data types: These include binary large objects (BLOBs) and character large objects (CLOBs).
7. Collection data types: These include arrays, sets, and maps.
8. User-defined data types: These are custom data types created by the user.
Overall, MySQL's API provides access to a wide range of data types, making it a versatile tool for managing and manipulating data in a variety of applications.
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: