zio/zio-quill
Quill is a Scala library that enables type-safe database queries by translating embedded Scala code into SQL or CQL. It provides a unified engine for query normalization, abstract syntax tree manipulation, and SQL generation across multiple backends including JDBC, Cassandra, Spark SQL, and OrientDB. The system supports both synchronous and asynchronous execution models, with specific integrations for ZIO and Pekko, and includes code generation utilities for database schemas.
51.8
Adequate · 3 August 2026
24k
lines of production code
Scala
primary language
4
bus factor · 155 authors in all
3
measurements over time
How it got here
2015–2016 · Cassandra and JDBC context implementation
This period focused on implementing new database context modules for Cassandra and various SQL databases, introducing mirror-based query probing, and establishing comprehensive test coverage for the core and database-specific components.
32 changes
2017–2021 · Engine consolidation and ZIO integration
This period focused on consolidating the Quill engine into a unified module and introducing ZIO-based database contexts for JDBC and Cassandra. It also added support for Spark SQL, OrientDB, and JDBC code generation, while significantly expanding test coverage across all new features.
51 changes
2022–2024 · ZIO and Doobie integration
This period focused on expanding Quill's ecosystem by introducing new JDBC context implementations for Doobie and ZIO, alongside migrating the Cassandra integration to Pekko. The work was heavily supported by comprehensive test coverage for these new features and existing database backends, ensuring robustness across multiple database engines and functional programming libraries.
18 changes
Survey your own repository
zio/zio-quill was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 3 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 5a5b8ae5fd — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.