PHP-MVC vs Play: What are the differences?
Developers describe PHP-MVC as "Simple and easy to understand MVC skeleton application". This project is - by intention - NOT a full framework, it's a bare-bone structure, written in purely native PHP ! The php-mvc skeleton tries to be the extremely slimmed down opposite of big frameworks like Zend2, Symfony or Laravel. 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.
PHP-MVC and Play can be primarily classified as "Frameworks (Full Stack)" tools.
PHP-MVC and Play are both open source tools. It seems that Play with 11.2K GitHub stars and 3.77K forks on GitHub has more adoption than PHP-MVC with 1.25K GitHub stars and 494 GitHub forks.
Coursera, Zalando, and Keen are some of the popular companies that use Play, whereas PHP-MVC is used by BetRocket, Digimedia ENVISION, and Scaffolder. Play has a broader approval, being mentioned in 112 company stacks & 47 developers stacks; compared to PHP-MVC, which is listed in 11 company stacks and 8 developer stacks.
What is PHP-MVC?
What is Play?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose PHP-MVC?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using PHP-MVC?
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?
Of all PHP frameworks, my best and only choice is Yii . Think of this: you have a MySQL database, it contains several tables. Now you want to setup a PHP-MVC site, firstly, you must create Models, Yii have a very handy tool called Gii, you can easily create model with Gii just by one click, Gii will read your database table columns and create PHP models automatically for you. Now you need Controller, still with Gii, it will automatically create all 4 php files for you with Insert/Delete/Update/Select even with Search function.
Well, now the most modern way is to have a RESTful API, that's even easier with Yii, you even don't need to care about all the columns, just 4 lines of code you can expose your database table as RESTful API with all GET/POST/PUT/DELETE support, even you change your database table columns, you don't need to change any PHP code.
For security, Yii have embedded authentication and RBAC support. For multi language, Yii have embedded i18n support, all with out-of-box. Just play with it, I bet you will love it.
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).