Spray VS Slick

Compare Spray vs Slick and see what are their differences.

Spray

A suite of scala libraries for building and consuming RESTful web services on top of Akka: lightweight, asynchronous, non-blocking, actor-based, testable (by spray)

Slick

Scala Language Integrated Connection Kit. Slick is a modern database query and access library for Scala (by slick)
Our great sponsors
  • Nanos - Run Linux Software Faster and Safer than Linux with Unikernels
  • Scout APM - A developer's best friend. Try free for 14-days
  • SaaSHub - Software Alternatives and Reviews
Spray Slick
1 6
2,538 2,498
0.0% 0.3%
0.0 8.5
almost 5 years ago 9 days ago
Scala Scala
GNU General Public License v3.0 or later 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.

Spray

Posts with mentions or reviews of Spray. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-04-21.
  • Scala: A Love Story
    4 projects | dev.to | 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.

Slick

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 2021-04-21.
  • Scala: A Love Story
    4 projects | dev.to | 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 | reddit.com/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: https://github.com/slick/slick/pull/2187
  • Just getting started with scala. Should i start with Scala 2 or just skip to scala 3 right away ?
    1 project | reddit.com/r/scala | 22 Mar 2021
    re: Slick, hopefully https://github.com/slick/slick/pull/2187 will land soon-ish. Stefan did much of the work himself a while back; now a volunteer is trying to put the finishing touches on.
  • From First Principles: Why Scala?
    11 projects | news.ycombinator.com | 11 Feb 2021
    The two major SQL libraries in the Scala ecosystem these days are Doobie (https://tpolecat.github.io/doobie/) and Slick (https://scala-slick.org/).

    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.

    11 projects | news.ycombinator.com | 11 Feb 2021
    they never said that, but it's basically abadonware. look at the commit history: https://github.com/slick/slick/commits/master you can also look at the contributors page: https://github.com/slick/slick/graphs/contributors the guys who primarly contributed to it basically left lightbend, and in 2019 he shifted his priorities.
  • Objection to ORM Hatred
    6 projects | news.ycombinator.com | 9 Feb 2021
    Many ORMs introduce a somewhat messy, complicated abstraction layer that doesn't actually get you the desired benefit in statically typed languages - compile time safety. Mainly because most languages do not have sufficiently powerful type systems.

    Exceptions are libraries like persist [1] for Haskell, Slick [2] for Scala, and - with caveats - Diesel [3] for Rust.

    But: manually mapping between the database domain and your domain objects is also a messy, error prone process that is wasted effort.

    My preferred solution is to stick with simple ORMs that just do simple mapping and provide a convenient query builder, without any heavy magic in the objects or any sort of automatic relationship logic (automatic fetching of joins, ...).

    [1] https://hackage.haskell.org/package/persistent

    [2] http://scala-slick.org/

    [3] http://diesel.rs/

What are some alternatives?

When comparing Spray 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

Http4s - A minimal, idiomatic Scala interface for HTTP

Anorm - The Anorm database library

Sorm - A functional boilerplate-free Scala ORM

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

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

Activate - Abandoned: Pluggable persistence in Scala

Akka HTTP - The Streaming-first HTTP server/module of Akka

Scala ActiveRecord - ActiveRecord-like ORM library for Scala