Dropwizard vs Play: What are the differences?
Developers describe Dropwizard as "Java framework for developing ops-friendly, high-performance, RESTful web services". Dropwizard is a sneaky way of making fast Java web applications. Dropwizard pulls together stable, mature libraries from the Java ecosystem into a simple, light-weight package that lets you focus on getting things done. 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.
Dropwizard and Play belong to "Frameworks (Full Stack)" category of the tech stack.
"Quick and easy to get a new http service going" is the top reason why over 23 developers like Dropwizard, while over 73 developers mention "Scala" as the leading cause for choosing Play.
Dropwizard and Play are both open source tools. Play with 11.2K GitHub stars and 3.77K forks on GitHub appears to be more popular than Dropwizard with 7.25K GitHub stars and 3.04K GitHub forks.
According to the StackShare community, Play has a broader approval, being mentioned in 112 company stacks & 47 developers stacks; compared to Dropwizard, which is listed in 51 company stacks and 12 developer stacks.
What is Dropwizard?
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
Sign up to get full access to all the companiesMake informed product decisions
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).