AI Coding 不只是工具升級-區域醫院醫療資訊系統協作開發與資訊團隊轉型實踐

Max Lai

蘇揮原 Mars Su
Ever spun up a Spark cluster just to process a few GB of parquet — only to realize it was complete overkill?
As data engineers, we've long lived between two extremes: pandas is too slow, Spark is too heavy. But there's a duck quietly waiting in that gap — and in 2026, there's also a fast-moving Rust-based challenger, Polars, sitting right next to it.
This talk is grounded in a real migration I led: an existing pandas-based ETL pipeline processing for anomaly analysis was migrated to DuckDB. You'll see a complete ETL pipeline running on a single machine using Python + DuckDB — reading multi-format data directly from Apache Iceberg on MinIO, transforming it with pure SQL, and loading it downstream without Spark cluster
Demo version:DuckDB v1.5.3 + Iceberg extension 0.11.1
I'll also show where DuckDB's Python API goes beyond "just SQL" — zero-copy interop with pandas/Polars DataFrames, type handling across engines.
I am a staff data engineer (Also Tech Leader) and in charge of design data architecture in network anomaly data team. I have introduced duckdb light weight pipeline mechanism so that data analyst & scientist can easy to process production telemetry data with Apache Iceberg OTF Lakehouse for anomaly detection algorithm. They would not be create on-demand spark cluster to extract data, which achieve cost & process effective (From minute level to seconds level).
One pip install duckdb. A complete ETL pipeline on a single machine — reading Apache Iceberg in MinIO, transforming with pure SQL, writing to your downstream target for analysis. No JVM. No cluster. No config files.

A Staff Data Engineer in TrendMicro. With over 8 years of experience in data engineering and machine learning. Mainly includes design & implement various data architecture. I am willing to pursue new knowledge and skill and share it so that I can make greater contributions in Data Engineering and ML field in the future.