Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The important thing to realize about Akka is that it's not an all-or-nothing environment. You can, to a large degree, mix and match different libraries to compose the system that makes sense for you. For instance, I have written apps that use <a href="https://github.com/codahale/dropwizard">Dropwizard</a> fronting a backend which uses Akka, without issue. I have also done the same with <a href="https://github.com/kirindave/clothesline">Clothesline</a> (implemented in Clojure, but with a <a href="https://github.com/tlockney/Clothesline-Scala">Scala wrapper</a>). And later this week, I hope to experiment with using <a href="https://github.com/unfiltered/Unfiltered">Unfiltered</a>'s <a href="https://github.com/unfiltered/unfiltered/tree/master/netty-websockets">websocket implementation</a> to sit in front of Akka and a RabbitMQ pipe for feeding near real-time data to the client browsers -- I specifically mention this example because the Unfiltered websocket impl sits on top of <a href="http://www.jboss.org/netty">Netty</a> rather than a servlet container).</p> <p><strong>Update</strong>: Since having written this answer a few years back, I've begun using <a href="http://spray.io/">Spray</a> exclusively for RESTful development with Akka. While pretty much any JVM REST library can be used, Spray fits very naturally into Akka's actor-based model and the library has clearly reached a level of maturity where it can easily be the default choice. The upcoming integration of Spray into Akka as the new akka-http module is a clear indication of this.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload