File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Groovy and the fly likes Introducing Grails in the Enterprise Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Languages » Groovy
Bookmark "Introducing Grails in the Enterprise" Watch "Introducing Grails in the Enterprise" New topic

Introducing Grails in the Enterprise

Tim Conner

Joined: Oct 02, 2007
Posts: 3
Glen and Peter,

I've dabbled in Grails and actually got a small web app up and running in a few hours. Needless to say I was pretty impressed. What do you think would be the best way of introducing Grails into a Java shop? Maintenance screens for larger Java projects? Complete smaller projects? Something else? Looking forward to checking out your book.

Tim Conner
Lanny Gilbert
Ranch Hand

Joined: Jun 11, 2002
Posts: 104
Just as "sneaking" Groovy into the enterprise by doing Unit Testing and proving how powerful, easy to use and flexible Groovy is to management, the same
model can be used for Grails. Find something small that could help your management do their job better (or developers do their job better), build that in Grails and
just watch management come on board
Peter Johnson

Joined: May 14, 2008
Posts: 5852

Using Grails to quickly prototype new apps also comes to mind. Especially potent if the people you are showing it to reprimand you for using so much time to do the prototype and you reply "Oh, I just thew this together this morning..."

JBoss In Action
Glen Smith

Joined: May 30, 2009
Posts: 8
Hi Tim,

Great question! I was just talking about this in another thread.

For me, the best way to gain traction is to kick some goals! I picked a few small projects off the client's "we need this now, but we don't have budget to spend a month building it" category. If you deliver on one of those in an afternoon, you'll start to get people's attention!

The most useful thing is that it starts dialog around Grails too. People asked me "But we will need to deploy it on Websphere one day". I could then explain that a Grails app is just a standard war file, standard bytecode, etc. Helps calm people down and gets them talking about Grails for bigger jobs.

All the best,


Vyas Sanzgiri
Ranch Hand

Joined: Jun 16, 2007
Posts: 686

Smaller projects, smaller requirements is the key.

I cannot believe when I have a couple of tables and the war is >30MB. Thats not all I find my grails app to be a memory hogger

===Vyas Sanzgiri===
My Blog
Peter Ledbrook

Joined: Jul 15, 2009
Posts: 25
Hi Vyas,

There is certainly a trade off between the benefits of Groovy and resource usage. I also believe that Groovy 1.6 uses more memory than the previous version, but that is the result of changes to make it execute faster. On the other hand, the memory usage may not be as bad as you fear. Are you using something like the JMX console to see the Java heap usage?

Grails has a lot of dependencies, and many of the plugins add even more. That's why the WAR file is so large. You might be interested in Glassfish v3, which I believe has a shared library mode. This shares the Grails dependencies between all deployed Grails applications, so the application WAR file is significantly smaller (of the order of a few megabytes).


Vyas Sanzgiri
Ranch Hand

Joined: Jun 16, 2007
Posts: 686

Yes I am looking into the shared library thing. But we have tomcat and don't want to introduce any other app server.

No I am not using JMX and I could still bring the server to its knees thru a Grails app :-)
I agree. Here's the link:
subject: Introducing Grails in the Enterprise
It's not a secret anymore!