Netty vs Play: What are the differences?
Developers describe Netty as "Asynchronous event-driven network application framework". Netty is a NIO client server framework which enables quick and easy development of network applications such as protocol servers and clients. It greatly simplifies and streamlines network programming such as TCP and UDP socket server. On the other hand, Play is detailed as "The High Velocity Web Framework For Java and Scala". 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.
Netty can be classified as a tool in the "Concurrency Frameworks" category, while Play is grouped under "Frameworks (Full Stack)".
"High Performance" is the top reason why over 2 developers like Netty, while over 73 developers mention "Scala" as the leading cause for choosing Play.
Netty and Play are both open source tools. It seems that Netty with 19.7K GitHub stars and 8.92K forks on GitHub has more adoption than Play with 11.2K GitHub stars and 3.75K GitHub forks.
According to the StackShare community, Play has a broader approval, being mentioned in 111 company stacks & 46 developers stacks; compared to Netty, which is listed in 11 company stacks and 14 developer stacks.
What is Netty?
What is Play?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Netty?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Netty?
Some may wonder why did we choose Grails ? Really good question :) We spent quite some time to evaluate what framework to go with and the battle was between Play Scala and Grails ( Groovy ). We have enough experience with both and, to be honest, I absolutely in love with Scala; however, the tipping point for us was the potential speed of development. Grails allows much faster development pace than Play , and as of right now this is the most important parameter. We might convert later though. Also, worth mentioning, by default Grails comes with Gradle as a build tool, so why change?
Play is a central framework/component/library (not sure what to call things these days) in Scala. We <3 Scala, and therefore we <3 Play.
Play is on of several frameworks we are prototyping and vetting for various public-facing websites, and may ultimately be the framework behind the main datapile.io website.
I used Play to build a configuration UI for the service, which let you create and manage the menus (a hierarchical tree of options and actions).