From what I've seen of Groovy and Grails, its biggest hurdle is adoption. Why else would anyone resist using a language that improves on Java and a framework based on Rails?

Views: 143

Replies to This Discussion

Robert Dempsey said:
What I am looking for is performance comparisons of Groovy/Grails with other frameworks combined with Java such as Spring.

Hello Robert, Have you explored Scala programming? It gives you the short and flexibility of Groovy like expressiveness, but yet has good performance as close as to Java itself! Scala is static typed instead of dynamic though. Check out other post I made few days ago under Other JVM Group on this site see if you like it.
-Z
What needs to be performant and why? Things like Twitter are built on a notoriously slow platform (ie, Ruby on Rails) but it's plenty fast enough.

Grails is obviously slower than Spring MVC since it's built on old versions of Spring MVC and Spring WebFlow. Does it matter? For the vast majority of web sites the answer is trivially simple: No.

Scala is faster and slower than Java depending on what you're doing. Groovy is slower than both, but who cares? It's more than fast enough for what it's used for.

If you really need speed, write in assembly code. If you think that's not reasonable, then ask yourself why you're willing to sacrifice that speed to be able to write in Java. Then apply the same reasoning to why you would program in something like Grails.

Note that I'm not saying that you should use Grails, just that looking at performance without solid reasons *why* is well beyond foolish.
There are some performance issues (For example I have been told my IDE friendly specific typing can cause issues) that make Scala/Java better for some high volume projects. However, for simplicity and readability groovy is a better way to develop, IMHO

Jackie
To answer adoption - Grails is becoming more and more mainstream. Sky.com, Wired, and Walmart (specifically mp3.walmart.com) are some notable sites using Grails.

In benchmarking, yes, Grails is slower. But improvements are being made, both to Groovy and Grails itself.

And benchmarks are generally useless in the real world. Every application is different. Bad code, poor database design, poor technology choices, etc are going to have a far greater impact then the language used.

Where performance is an issue, you can always use Java (or Scala). In fact, much of the Grails framework is in Java, not Groovy. It all comes down to using the right tool for the job.

Also - in the age of distributed computing, I need to ask who cares if there is a 20-30% performance penalty. What does it matter if you need to spool up another VM or two in the cloud?

RSS

Happy 10th year, JCertif!

Notes

Welcome to Codetown!

Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.

When you create a profile for yourself you get a personal page automatically. That's where you can be creative and do your own thing. People who want to get to know you will click on your name or picture and…
Continue

Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.

Looking for Jobs or Staff?

Check out the Codetown Jobs group.

 

Enjoy the site? Support Codetown with your donation.



InfoQ Reading List

AI Is Moving up the Software Lifecycle: From Code Review to PRD Governance

Technology companies are extending AI beyond code generation into earlier stages of the software lifecycle, including PRD validation, design inputs, and code review. Initiatives from Uber, DoorDash, and Cloudflare highlight a shift toward AI-driven governance layers that evaluate engineering artifacts before implementation while preserving human oversight across the development pipeline.

By Leela Kumili

Presentation: Rules for Understanding Language Models

Naomi Saphra discusses 5 rules governing language model behavior, breaking down why LLMs act like populations rather than individuals. She explains how tokenization creates strange semantic blind spots and highlights the mechanics of sycophancy, showing how models leverage subtle data associations to match user biases and demographics - even guessing political views based on favorite sports teams.

By Naomi Saphra

Article: Beyond CLEAN and MVP: Architecting an Offline-first Reactive Data Layer in Android

With the Reactive Data Layer Architecture (RDLA), you establish a clear boundary between public data APIs and private, framework-specific data-source implementations. Your presentation layer operates in a purely reactive manner, observing data changes rather than procedurally querying them. RDLA also simplifies testing by encouraging you to program to interfaces and use clean seeding patterns.

By Mervyn Anthony

Lucide Releases Version 1.0, Removing Brand Icons and Cutting Bundle Size for Millions of Projects

Lucide has released version 1.0 of its open-source icon toolkit, marking its first stable major release. The update features over 1,600 icons and removes trademarked brand icons due to legal and design concerns. Significant performance improvements have also been made, reducing package size and adding context providers for various frameworks. Users upgrading should be aware of breaking changes.

By Daniel Curtis

Presentation: The Time It Wasn't DNS

Sean Klein discusses why "human error" is a dangerous myth in complex systems. Sharing the inside story of Azure’s 2023 global WAN outage, he explains how modern incident analysis looks past the "Five Whys" to uncover systemic issues. Learn how engineering leaders can move away from blame, improve Standard Operating Procedures, and design resilient systems that actively protect their engineers.

By Sean Klein

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service