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

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

OpenAI Begins Article Series on Codex CLI Internals

OpenAI recently published the first in a series of articles detailing the design and functionality of their Codex software development agent. The inaugural post highlights the internals of the Codex harness, the core component in the Codex CLI.

By Anthony Alford

Etleap Launches Iceberg Pipeline Platform to Simplify Enterprise Adoption of Apache Iceberg

Etleap has recently launched the Iceberg pipeline platform, a new managed data pipeline layer designed to let enterprises adopt Apache Iceberg without building or maintaining a complex custom stack.

By Craig Risi

Article: Working with Code Assistants: The Skeleton Architecture

Prevent AI-generated tech debt with Skeleton Architecture. This approach separates human-governed infrastructure (Skeleton) from AI-generated logic (Tissue) using Vertical Slices and Dependency Inversion. By enforcing security and flow control in rigid base classes, you constrain the AI to safe boundaries, enabling high velocity without compromising system integrity.

By Patrick Farry

Dev Proxy v2.1 Introduces Configuration Hot Reload and Stdio Traffic Proxying

The Dev Proxy team has released Dev Proxy version 2.1, introducing new features aimed at improving developer productivity and simplifying local testing workflows. This release focuses on faster iteration, better support for modern development tools, and several refinements across the proxy and its related tooling.

By Almir Vuk

MongoDB Introduces Embedding and Reranking API on Atlas

MongoDB has recently announced the public preview of its Embedding and Reranking API on MongoDB Atlas. The new API gives developers direct access to Voyage AI’s search models within the managed cloud database, enabling them to create features such as semantic search and AI-powered assistants within a single integrated environment, with consolidated monitoring and billing.

By Renato Losio

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service