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: 103

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

Presentation: The Architecture of Developer Experience: Where Product, Platform, and Operations Meet

The panelists discuss designing platform architecture where product, platform, and operations meet. Experts share best practices for reducing cognitive load, balancing core ops vs. innovation, measuring success (lead time, cost avoidance), and enabling developers through self-service and golden path deviations.

By Ran Isenberg, Garima Bajpai, Stephane DiCesare, Martin Reynolds, Faizan Panwala, Renato Losio

AWS Lambda Rust Support Reaches General Availability

AWS has elevated Rust support in Lambda from experimental to generally available, empowering developers to create high-performance, memory-safe serverless applications. This milestone enhances developer confidence, backed by AWS support and SLA. While it offers speed comparable to C++, challenges such as lengthy SDK compile times and increased binary sizes remain key considerations.

By Steef-Jan Wiggers

Developing and Deploying Software in a Sustainable Way

Sustainable APIs benefit most from minimalism, Jochen Joswig said at OOP Conference . Deployment should consider energy, usage, carbon intensity, hardware acquisition. Remote work, long device lifespans, and green office practices can lower emissions. Efficient CI, selective builds, smaller artefacts, and optimized assets can further reduce energy use.

By Ben Linders

Enhancing Reliability Using Service-Level Prioritized Load Shedding at Netflix QCon SF 2025

At QCon San Francisco, Netflix engineers unveiled their advanced Service-Level-Prioritized Load-Shedding strategy, enhancing reliability during traffic spikes. By prioritizing high-value requests and automating management across microservices, they safeguard user experience and system stability. Key insights stress prioritization, automation, and structured load shedding for optimal resilience.

By Steef-Jan Wiggers

AI Agents Fail Manipulation Tests in Microsoft's Magentic Marketplace Simulation

Researchers at Microsoft, working in collaboration with Arizona State University, have introduced Magentic Marketplace, an open-source simulation environment designed to study how LLM-based agents behave in multi-agent economic systems. The platform addresses a growing need in AI research as autonomous agents gain capabilities in software development.

By Vinod Goje

© 2025   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service