| Tool | Strengths | Weaknesses | |------|-----------|-------------| | (PDI fork) | Modern UI, better plugins, active open source | Smaller ecosystem | | Apache NiFi | Real-time, web UI, data provenance | Steeper learning curve | | Airbyte | ELT-focused, modern connectors | Less transform flexibility | | Talend Open Studio | Broader connector set | Heavier IDE, less agile | | dbt (ELT approach) | SQL-centric, Git-friendly | Needs a data warehouse target | Summary Table – PDI CE Features at a Glance | Category | Status | |----------|--------| | Drag-and-drop ETL design | ✅ Excellent | | Database & file connectors | ✅ Good (over 200 steps) | | Job orchestration | ✅ Basic but functional | | Performance (single node) | ✅ Good | | Scalability (cluster) | ❌ Poor / unstable | | Scheduling | ❌ No (use cron) | | Version control integration | ✅ Manual (Git with file repo) | | Security / roles | ❌ None | | Real-time data | ❌ No | | Free & open source | ✅ Yes (GPL/LGPL) | | Active community support | ⚠️ Declining (moved to Hop) | Final Verdict: Download PDI CE if you need a free, visual, mature batch ETL tool and can accept manual scheduling, no built-in collaboration, and declining official support. For new projects, consider Apache Hop (active fork) or modern ELT tools unless you have legacy PDI transformations to maintain.