How l1xnan/duckling works
Project type and purpose
• Duckling is a desktop “full-stack” application built with Tauri.
• Its goal is to let users quickly browse Parquet/CSV files and query several databases (DuckDB, SQLite, PostgreSQL, MySQL, ClickHouse, Doris/StarRocks).
High-level architecture overview
a. User Interface (UI) Layer
b. IPC / Tauri Command Layer
c. Backend Library Layer
d. Data Sources Layer
Main components
a. UI Layer (src/ + public + index.html)
• Built with Vite, React, TypeScript.
• Pages (src/pages), Components (src/components), Hooks (src/hooks), State Stores (src/stores).
• Assets (src/assets, assets/) and global styles.
b. IPC / Tauri Command Layer (src-tauri)
• src-tauri/src/main.rs: Tauri setup & WebView host.
• src-tauri/src/cmd.rs: defines commands exposed to the UI (e.g., open file, run query).
• tauri.conf.json, build scripts.
c. Backend Library Layer (connector crate)
• connector/src/lib.rs: public API the Tauri commands call.
• Dialect modules (connector/src/dialect/*): ClickHouse, DuckDB, MySQL, PostgreSQL, SQLite, File, Folder.
• Common utilities (types.rs, utils.rs, api.rs).
d. Data Sources Layer
• Local file system: Parquet/CSV (handled by File and Folder dialects).
• Embedded DB: DuckDB, SQLite.
• External DBs: PostgreSQL, MySQL (including Doris/StarRocks compatibility), ClickHouse (native port).
Relationships & data flows
• UI triggers user actions (open folder, run SQL).
• UI → sends invoke call over Tauri IPC → Tauri Command Layer.
• Command Layer → calls functions in the connector library.
• Connector routes to appropriate dialect module → interacts with the data source.
• Results (tables/JSON) return up the stack → UI renders via React components.
Architectural patterns & principles
• Clear separation of concerns:
• Presentation (React) vs. business logic (connector) vs. host environment (Tauri).
• Asynchronous, request-response model over a secure IPC channel.
Relevant technologies & libraries
• Frontend: React, Vite, TypeScript, Zustand (or similar) for state, Monaco editor integration, Tailwind or CSS modules.
• Backend: Tauri (Rust), Tokio (async), crates for each database (e.g., duckdb-rs, rusqlite, tokio-postgres, mysql_async, clickhouse-rs), Parquet reader.
• Build & config: Cargo, pnpm, ESLint, Prettier, GitHub Actions.