Menu
Do anyone know which web server is used by play! framework?
I'm planning to prototype a small intranet app using Play! and I am wondering whether I should use the default play web server or Apache or IIS as used internally.
I don't predict several instances of the application running nor a need for load balancing.
881
Play Framework makes it easy to build web applications with Java & Scala. Play is based on a lightweight, stateless, web-friendly architecture. Built on Akka, Play provides predictable and minimal resource consumption (CPU, memory, threads) for highly-scalable applications.
Play comes with two configurable server backends, which handle the low level work of processing HTTP requests and responses to and from TCP/IP packets. Starting in 2.6. x, the default server backend is the Akka HTTP server backend, based on the Akka-HTTP server. Prior to 2.6.
Play is rock-solid and used by hundreds of thousands of Java and Scala developers every month. Play is still extremely relevant to today's application and web development and has a passionate and very capable community around it ensuring that it has many good years left.
A play application follows the MVC architectural pattern applied to the Web architecture. This pattern splits the application into separate layers: the Presentation layer and the Model layer. The Presentation layer is further split into a View and a Controller layer.
The internal server is Netty.
Unless you are forced to deploy a Play application in a servlet container, don't do it. Play performs better on Netty as it doesn't need to jump through hoops to support the servlet standard, which shaves off quite a bit of overhead.
My preferred way of deploying Play is attached to a screen session, but "play start" should also do the trick :)
167
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
