Anorm VS Slick

Compare Anorm vs Slick and see what are their differences.


The Anorm database library (by playframework)


Slick (Scala Language Integrated Connection Kit) is a modern database query and access library for Scala (by slick)
Our great sponsors
  • InfluxDB - Access the most powerful time series database as a service
  • SonarQube - Static code analysis for 29 languages.
  • SaaSHub - Software Alternatives and Reviews
Anorm Slick
1 14
226 2,606
0.4% 0.3%
8.8 9.3
5 days ago about 16 hours ago
Scala Scala
Apache License 2.0 BSD 2-clause "Simplified" License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of Anorm. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-08-31.


Posts with mentions or reviews of Slick. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-06-02.
  • Sketch of a Post-ORM
    14 projects | | 2 Jun 2023
    The Scala ecosystem has a few ways to do composable type-safe query building, e.g. Slick[0] or more recently Quill[1]. . I believe both also have ways to do compile-time string interpolation (e.g. sql"""select * from users where id = ${}""") which generate prepared statements (I know Slick does prepared statements. Quill has similar macros but I haven't looked into how safe they are to use).


  • Database abstraction library which allows a clean domain model
    2 projects | /r/scala | 20 Jan 2023
    With all this in mind, I landed at the first candidate: slick from that you all probably know.
  • Scala 3 migration: 7 benefits that outweigh the risks
    2 projects | /r/scala | 3 Nov 2022
    I think Slick's current priority is also getting in Scala 3 support:
  • Slick 3.4.x is here!
    3 projects | /r/scala | 18 Sep 2022
    Future releases might not be announced here. To get notified, go to, click the Watch dropdown button at the top, select Custom, check Releases, and click Apply.
  • Is there any good resource for learning Slick (3.x)?
    2 projects | /r/scala | 2 Sep 2022 now I use slightly lower version of slick so this might be an upgrade that resolves (I do recall using it in 21 and it was still buggy and I filed a ticket, which I cannot find at the moment), but given a complex enough query (we have one in PROD which has tons of flexibility in terms of filters that can be passed in) but it also makes for complex code.
  • Slick 3.4.0 is imminent
    2 projects | /r/scala | 16 Aug 2022
    I started writing a reply but then I realized it would be long and depends on exactly what you mean, so maybe it's better to post the question in
    2 projects | /r/scala | 16 Aug 2022
    You can see the draft release notes here and the upgrade guide at The latest docs are at
  • Scala: A Love Story
    4 projects | | 21 Apr 2021
    I purchased the very entertaining book Seven Languages in Seven Weeks. Although I found Haskell fascinating and tempting, I knew it was unrealistic to introduce it in our company. Scala on the other hand looked like it could be the holy grail: All the characteristics I was looking for, no need to abandon the JVM and its cornucopia of tools and libraries, and the possibility for coexistence with Java and therefore incremental adoption. After implementing some simple programs to identify any immediate risks of committing to the language and its ecosystem, I started to introduce Scala in customer projects. Luckily, I was fortunate enough to work with open-minded, curious, and ambitious team members who were also experienced enough to appreciate the benefits of the language. We immediately applied our experience with functional programming, and embraced immutability. Libraries like Slick and Akka HTTP (we actually started out with its predecessor, Spray) made building database-backed REST services a breeze. And the resulting code was robust and highly maintainable. Scala's expressive type system and type inference made it easy to build a restrictive, consistent domain model without bloating the code. There was virtually no overhead. Any boilerplate could be easily abstracted out. In the end, the application code felt natural, concise and elegant. Programming was fun again.
  • Scala 3.0.0-RC2 Has Landed
    5 projects | /r/scala | 30 Mar 2021
    Slick is community-maintained these days. It appears likely this PR adding Scala 3 support will cross the finish line before too much longer:
  • From First Principles: Why Scala?
    11 projects | | 11 Feb 2021
    The two major SQL libraries in the Scala ecosystem these days are Doobie ( and Slick (

    With Doobie you manually write your queries, and then map the results into the objects in your domain model. Nothing is generated for you. OTOH, nothing is hidden and you are free to write queries as optimized and specialized as you need. The real selling point of Doobie is a typesafe API for manipulating and combining queries, and fragments of queries, into larger wholes. This works very well when your application interfaces with a database it doesn't own.

    With Slick you get access to a DSL that lets you layout how your tables look. From there Slick offers an api that let's you treat SQL tables as-if they are basically mutable collections, with Slick handling all the SQL generation itself. You also get DDL, so that you can automate db creation and upgrades. This work very well when your application owns and controls the database it is connecting to.

    Both of these have diverged from that traditional ORM model. Slick bills itself as FRM, or Functional Relational Mapping. And Doobie is embedded queries on steroids.

What are some alternatives?

When comparing Anorm and Slick you can also consider the following projects:

doobie - Functional JDBC layer for Scala.

Quill - Compile-time Language Integrated Queries for Scala

ScalikeJDBC - A tidy SQL-based DB access library for Scala developers. This library naturally wraps JDBC APIs and provides you easy-to-use APIs.

Squeryl - A Scala DSL for talking with databases with minimum verbosity and maximum type safety

Sorm - A functional boilerplate-free Scala ORM

Clickhouse-scala-client - Clickhouse Scala Client with Reactive Streams support

cats-effect - The pure asynchronous runtime for Scala

Phantom - Schema safe, type-safe, reactive Scala driver for Cassandra/Datastax Enterprise

Activate - Abandoned: Pluggable persistence in Scala

Elastic4s - Elasticsearch Scala Client - Reactive, Non Blocking, Type Safe, HTTP Client