Editing Portal:Databases (section)

=== Analytical databases and newer data engines ===

Modern data development includes embedded analytics, columnar storage, search systems, time-series databases, cloud APIs, and data lake tools. Perl’s position here is mixed but still useful. It is not usually the fashionable first-choice language for new machine-learning notebooks or cloud-native analytics dashboards, but it remains effective for automation, ingestion, integration, transformation, reporting, and system glue.

'''DuckDB''' is a good example of a newer database model that fits Perl’s traditional strengths. DuckDB is an embedded analytical SQL database, and `DBD::DuckDB` provides a DuckDB database driver for Perl’s DBI module.<ref>MetaCPAN, “DBD-DuckDB,” https://metacpan.org/dist/DBD-DuckDB, accessed July 3, 2026.</ref> This is significant because it lets Perl participate in modern local analytics workflows while preserving the familiar DBI pattern.

'''ClickHouse''' is another example from the modern analytical database world. Perl has a `ClickHouse` module described as a Perl interface to the ClickHouse OLAP database, though its own documentation describes it as experimental and not yet a DBI-compatible driver.<ref>MetaCPAN, “ClickHouse,” https://metacpan.org/pod/ClickHouse, accessed July 3, 2026.</ref> That illustrates a broader pattern: Perl often has access to newer databases, but some drivers may be less mature than the classic DBI drivers for PostgreSQL, SQLite, MySQL, and MariaDB.

Perl can also interact with many newer “databases” through HTTP APIs rather than native drivers. This includes search services, cloud databases, graph systems, object stores, vector databases, and SaaS data platforms. In these cases, Perl’s JSON support, HTTP client modules, streaming parsers, and text-processing tools are often more important than a traditional database driver.