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

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

How Observability and Telemetry Can Enhance the Practice of Software Engineering

Observability must evolve with serverless, event-driven architectures. OpenTelemetry can decouple telemetry from vendors, letting developers emit consistent, high-quality data that explains real system behavior. Shared vocabularies and good telemetry make debugging faster and improve reliability, speed, and developer productivity.

By Ben Linders

Presentation: How to Build an Exchange: Sub Millisecond Response Times and 24/7 Uptimes in the Cloud

Frank Yu shares Coinbase’s engineering philosophy for building resilient, fair, and fast financial exchanges. He explains the power of a single-threaded architecture combined with the Raft consensus algorithm to maintain 24/7 availability. He discusses how determinism enables zero-downtime rolling deployments and the ability to replay production logs for perfect bug reproduction.

By Frank Yu

Dropbox Collaborates with GitHub to Reduce Monorepo Size from 87GB to 20GB

Dropbox reduced its backend monorepo from 87GB to 20GB by optimizing Git delta compression in collaboration with GitHub. The changes improved clone times, CI performance, and developer velocity, highlighting how repository storage inefficiencies can impact large-scale engineering workflows.

By Leela Kumili

Presentation: Panel: Building a Culture that Works

The panelists share insights on evolving company culture. They discuss leveraging feedback loops, lending social capital, and the friction between legacy bureaucracy and agile engineering. The panel explains how to maintain cohesion in remote teams and use interviews to uncover the true "unmanicured" culture of a firm.

By Nicky Wrightson, Suhail Patel, Lesley Cordero, Matthew Card, Natan Žabkar Nordberg

Cloudflare Sandboxes Reach General Availability, Giving AI Agents Persistent Isolated Environments

Cloudflare has released Sandboxes and Containers into general availability, providing persistent isolated Linux environments for AI agent workloads. New capabilities include secure credential injection via egress proxy, PTY terminal support, persistent code interpreters, filesystem watching, and snapshot-based session recovery. Active CPU pricing charges only for used cycles.

By Steef-Jan Wiggers

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service