Spray VS Akka HTTP

Compare Spray vs Akka HTTP 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)
Our great sponsors
  • Scout APM - A developer's best friend. Try free for 14-days
  • Nanos - Run Linux Software Faster and Safer than Linux with Unikernels
  • SaaSHub - Software Alternatives and Reviews
Spray Akka HTTP
1 2
2,538 1,213
-0.0% 1.2%
0.0 8.8
almost 5 years ago 6 days ago
Scala Scala
GNU General Public License v3.0 or later GNU General Public License v3.0 or later
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.

Akka HTTP

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

What are some alternatives?

When comparing Spray and Akka HTTP you can also consider the following projects:

Http4s - A minimal, idiomatic Scala interface for HTTP

Finch.io - Scala combinator library for building Finagle HTTP services

scalaj-http - Simple scala wrapper for HttpURLConnection. OAuth included.

sttp - The Scala HTTP client you always wanted!

Dispatch - Scala wrapper for the Java AsyncHttpClient.

Scalaxb - scalaxb is an XML data binding tool for Scala.

Tubesocks - A comfortable and fashionable way to have bi-directional conversations with modern web servers.

featherbed - Asynchronous Scala HTTP client using Finagle, Shapeless and Cats

Netcaty - Simple net test client/server for Netty and Scala lovers