About Boni Satani

Boni Satani is a Java Technology Consultant working with Cygnet Infotech. He has undertaken various Projects in Java Web Application Development and J2EE Application Development including their maintenance and migration.

The Pros and Cons of Play and Grails Java Framework

Frameworks simplify the process of application development by providing some helpful features to programmers. Java frameworks are often used by developers and thanks to their popularity; you can find a range of Java development frameworks in the market. Newbie developers often post a common question in forums, “which Java framework is the best?”

First of all, there is no one framework that is best because all of them have some advantages and disadvantages. Therefore, you must decide considering the project requirements. You must think about the key factors like scalability, complexity, deadline and, obviously, budget.
Today, we will discuss the pros and cons of two very popular Java frameworks- Play and Grails.



It’s one of the best frameworks currently available in the market. Developers love it because it is easily programmable, scalable and powerful. Play is programmable in Scala language.

Let’s take a look at some of the major features of Play.

  1. Developers often make small changes in coding during the development and testing phase to identify the best possible solution. Generally, they need to restart the system to see the changes they have made. However, if you use Play, all you need to do is refresh the browser to see the recent changes immediately.
  2. It has only one XML file for configuration and thankfully, most of the configurations are either default or automatically set.
  3. It does not use Servlets API. Therefore, developers can use hot swapping.

What are the advantages?

  • It allows you to develop faster so that you can work on multiple projects at the same time and deliver all of them within deadline.
  • Testing the application is very easy and testing provides authentic results.
  • The user interface is intuitive.

What are the disadvantages?

  • Scala is a complicated programming language and thus, novice programmers may not feel very comfortable using it.
  • It does not offer backward compatibility. For example, Play 2 is not compatible with Play 1. So, if you are planning to migrate to an existing app, you have to do all the tasks once again.
  • It’s hard to understand the architecture and things going behind the scene.
  • There are lots of plug-ins but they are not stable.


It’s another open source Java development framework. Grails is built upon Hibernate, Spring and SiteMesh. It utilizes Groovy as the coding standard and since Groovy is similar to Java, programmers think it is easier to begin with Grails.

Let’s take a look at the major features of Grails.

  1. You can use the same codes repeatedly to perform different actions and save time.
  2. XML processing is easy.

What are the advantages?

  • It provides a rapid development cycle.
  • If you are dealing with a small or medium-size project, Grails is ideal for you.
  • The framework offers a range of plug-ins to make your ob simple.
  • The documentation is really impressive.
  • The setup process is very simple. Therefore, you should be able to start building an app in an hour.
  • Simple GORM. It may take some time to learn but once you are familiar with it, it’s absolutely wonderful.
  • You can see the changes by hitting the refresh button.
  • Less CSS framework plug-ins. Hence, it’s easier to manage the CSS.
  • Dynamic configuration feature. Therefore, you can change the configuration without server restart.

What are the disadvantages?

  • You have to deal with runtime language. Its negative quality is that it is error prone and you have to bear with other cons of runtime language.
  • If you are working on a multi threaded app, GORM can be problematic for you.
  • You have to buy IntelliJ Idea because other IDE’s either don’t have or provide limited support.
  • Developers generally declare variables with “def” which is equivalent to “object”. It’s very hard to maintain.
  • Interpreted languages increase weight and that directly affects the run time.
  • You must learn Groovy coding.
  • It works with GORM but not with any other ORMs.
  • Integration process is complicated.

So, as you can see, both frameworks have some pros and cons. Therefore, you should not rely on other people’s opinions. Choose either Play or Grails considering the requirements of your project.

Related Whitepaper:

Bulletproof Java Code: A Practical Strategy for Developing Functional, Reliable, and Secure Java Code

Use Java? If you do, you know that Java software can be used to drive application logic of Web services or Web applications. Perhaps you use it for desktop applications? Or, embedded devices? Whatever your use of Java code, functional errors are the enemy!

To combat this enemy, your team might already perform functional testing. Even so, you're taking significant risks if you have not yet implemented a comprehensive team-wide quality management strategy. Such a strategy alleviates reliability, security, and performance problems to ensure that your code is free of functionality errors.Read this article to learn about this simple four-step strategy that is proven to make Java code more reliable, more secure, and easier to maintain.

Get it Now!  

6 Responses to "The Pros and Cons of Play and Grails Java Framework"

  1. Soroosh Sarabadani says:

    In Play framework you can use java language and you are not restricted to use scala!

  2. Caleb holt says:

    It is ridiculous that you say you must buy intellij to get use grails. The official ide which is based on the spring tool suite(which is based on eclipse) has many features and works great for grails development. Telling people they have to pay money to use it would keep them from even trying grails and creates a very unfair analysis of pros vs cons.

  3. wolkott says:

    Grails also works very well with hibernate mapped/annotated classes so you are quite incorrect in saying it does not work with any other ORM.

  4. Rajesh Rao says:

    Stop doing comparison of frameworks if at the last all you can say is “Choose the framework according to your project requirements”. At least give the readers some examples and scenarios like for which type of projects you should choose playframework and for which type of projects you should go for grails.

  5. Eduardo says:

    “Boni Satani is a Java Technology Consultant working with Cygnet Infotech. He has undertaken various Projects in Java Web Application Development and J2EE Application Development including their maintenance and migration.” ¿WTF? It’s the worst analysis I read in months……

  6. Birendra Dhami says:

    What a bad analysis. Your article clearly says you are against Grails.

Leave a Reply

6 + one =

Java Code Geeks and all content copyright © 2010-2014, Exelixis Media Ltd | Terms of Use | Privacy Policy
All trademarks and registered trademarks appearing on Java Code Geeks are the property of their respective owners.
Java is a trademark or registered trademark of Oracle Corporation in the United States and other countries.
Java Code Geeks is not connected to Oracle Corporation and is not sponsored by Oracle Corporation.
Do you want to know how to develop your skillset and become a ...
Java Rockstar?

Subscribe to our newsletter to start Rocking right now!

To get you started we give you two of our best selling eBooks for FREE!

Get ready to Rock!
You can download the complementary eBooks using the links below: