GraPHP vs Play: What are the differences?
GraPHP: A PHP graph DB web framework *. The goal of this project is to build a lightweight web framework with a graph DB abstraction. It should be very easy to create the graph schema with no knowledge of of how the data is stored. Also, the schema should be incredibly flexible so you should never need migrations when adding new models (nodes), connections (edges), or data that lives in nodes; *Play:** 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.
GraPHP and Play belong to "Frameworks (Full Stack)" category of the tech stack.
GraPHP 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 GraPHP with 135 GitHub stars and 5 GitHub forks.
What is GraPHP?
What is Play?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose GraPHP?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using GraPHP?
What companies use GraPHP?
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).