Scala framework for a Rest API Server? [closed]

Question

We are thinking on moving our Rest API Server (it is inside the web service, on Symfony PHP) to Scala for several reasons: speed, no overhead, less CPU, less code, scalability, etc. I didn't know Scala until several days ago but I've been enjoying what I've been learning these days with the Scala book and all the blog posts and questions (it's not so ugly!)

I have the following options:

• build the Rest API Server from scratch
• use a tiny Scala web framework like Scalatra
• use Lift

Some things that I will have to use: HTTP requests, JSON output, MySQL (data), OAuth, Memcache (cache), Logs, File uploads, Stats (maybe Redis).

What would you recommend?

Answer 1

In no particular order:

• Akka HTTP
• Spray
• Paypal squbs (Akka/Spray)
• DropWizard
• REST.li
• http4s
• Blue Eyes
• Finagle - A fault tolerant, protocol-agnostic RPC system
• Play! and Play-mini! (article) (tutorial)
• Lift / Lift JSON.- makes it simple to provide REST services.

Answer 2

I'm going to recommend Unfiltered. It's an idiomatic Web framework that does things "the Scala way" and is very beautiful.

Answer 3

Take a look at Xitrum (I'm its author), it provides everything you listed. Its doc is quite extensive. From README:

Xitrum is an async and clustered Scala web framework and web server on top of Netty and Hazelcast:

• Annotation is used for URL routes, in the spirit of JAX-RS. You don't have to declare all routes in a single place.
• Async, in the spirit of Netty.
• Sessions can be stored in cookies or clustered Hazelcast.
• In-process and clustered cache, you don't need separate cache servers.
• In-process and clustered Comet, you don't need a separate Comet server.

Answer 4

I would add two more options: akka with built-in JAX-RS support, and simply using JAX-RS directly (probably the Jersey implementation). While arguably less "Scala-y" than others (relying upon annotations to bind parameters and paths), JAX-RS is a joy to use, cleanly solving all of the problems of web service coding with minimal footprint. I've not used it via akka, I would anticipate it being excellent there, getting impressive scalability via it's continuation-based implementation.

Answer 5

Take a look at Finch, a Scala combinator library for building Finagle HTTP services. Finch allows you to construct complex HTTP endpoints out of the number of predefined basic blocks. Similarly to parser combinators, Finch endpoints are easy to reuse, compose, test, and reason about.

Answer 6

All good answers so far. One point in Lift's favor is its RestHelper, which can make it quite easy to write short, elegant API methods. In addition, all the other things you want to do should be quite straight-forward to implement in Lift. That being said, Memcache might be not be necessary.

Answer 7

A little late on the scene but I would definitely recommend using Bowler framework for creation of REST API's. It small, to the point and automatic case class conversion support!