when should we use data fusion over etl data flows
Best Answer
-
Fusion is fantastic for relatively simple joins on large datasets that number in the tens of millions of rows and greater.
The ETL and MySQL dataflows are different ways to accomplish the same end goal, allowing the user to pick the method they are most comfortable with. Some users work best in SQL, so the MySQL ETL recreates that, whereas some people prefer visual drag and drop dataflows which is Magic ETL.
All things being equal, I believe that Magic ETL is slightly more performant than MySQL ETL however.
The choice further comes down to how complicated some of your dataflows are/can be, and how they will be managed. It's easier to see what's happening from a high level with Magic, but can data transformations tricky to perform. MySQL allows for basically any data transformation to occur, but you need to go into each transform to view the logic.
0
Categories
- 7.6K All Categories
- Connect
- 917 Connectors
- 242 Workbench
- 473 Transform
- 1.8K Magic ETL
- 60 SQL DataFlows
- 445 Datasets
- 33 Visualize
- 198 Beast Mode
- 2K Charting
- 8 Variables
- 1 Automate
- 348 APIs & Domo Developer
- 82 Apps
- Workflows
- 14 Predict
- 3 Jupyter Workspaces
- 11 R & Python Tiles
- 241 Distribute
- 59 Domo Everywhere
- 241 Scheduled Reports
- 14 Manage
- 35 Governance & Security
- 19 Product Ideas
- 1.1K Ideas Exchange
- Community Forums
- 15 Getting Started
- 1 Community Member Introductions
- 49 Community News
- 18 Event Recordings
- 579 日本支部