Grails Experience :: Should we use Grails?

Grails LogoRecently I was asked this question about my experience with Grails that I thought was worth sharing:

Have you ever been on a grails/groovy project that failed because of
* limitations/faults in the technology itself
* the grails/groovy learning curve

Here was my response:

Professionally, I have been a part of seven large Grails projects (+ more smaller endeavors). Of those seven, three of them were moving to grails from another framework, two due to failures with other teams/technologies and one was a Spring to Grails migration.

None of those seven failed because of Grails – in fact – the clients were very happy with the speed of development. Especially the rescue missions that had *very* tight timelines. At one startup we had a quite substantial Grails app that had a Flex front-end. When developing new stories, we found that the Flex front-end took ~80% of the time whereas the Grails components took 20% of our time and were very reasonable to test and maintain.

I’m not saying that we didn’t run into issues in learning curve or even issues/intricacies of Grails itself, but rather that we were able to make excellent progress and address those issues. The community and open source nature of both Groovy and Grails turned out to be extremely helpful when addressing technical challenges.

On one of the projects that had a very tight timeline most of the developers weren’t even Java developers, but had done some Django, PHP, RoR experience. The project was quite successful. We were able to accomplish more in less than a month then another firm was able to do in six months before declaring failure with another framework.

To add to my response, I would say that since testing is a priority and a first class citizen in Grails, it definitely added to the ongoing stability of the projects over time. The sections of code that were tested typically ended up being much more coherent and stable over the course of the projects life.

How would you respond to that question?

About the Author

Object Partners profile.

One thought on “Grails Experience :: Should we use Grails?

  1. Joshua Davis says:

    I would agree with Colin here that my client was amazed at the reduced development time for the backend components. The front end and user experience work was about the same ratio as he stated in his post.

    Also, the components that were tested using Grails unit testing were the most stable as well. In my opinion testing the components using Grails unit testing is another large advantage over other frameworks.

Leave a Reply to Joshua Davis Cancel reply

Your email address will not be published. Required fields are marked *

Related Blog Posts
React Server Components
The React Team recently announced new work they are doing on React Server Components, a new way of rendering React components. The goal is to create smaller bundle sizes, speed up render time, and prevent […]
Jolt custom java transform
Jolt is a JSON to JSON transformation library where the transform is defined in JSON. It’s really good at reorganizing the json data and massaging it into the output JSON you need. Sometimes, you just […]
Page Object Model for UI Testing
How to make a multi-handled range input
The HTML range input is a great way to allow your users to manipulate a numeric value using their mouse. The range input that is currently provided by browsers only supports a single handle, which […]