groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Graeme Rocher <>
Subject Re: Help with pitching Groovy and Grails
Date Thu, 23 Feb 2017 19:32:37 GMT
The argument "using reflections in JVM is slow period" is stupid because so
much of all JVM frameworks is reflection based.

Spring used reflection for proxies, AOP, data binding, pretty much

Hibernate uses reflection to convert objects to and from the database.

The reflection part of the application is never going to be your
bottleneck. It will be your database, or message queue or whatever.

Apart from that with modern Groovy (@CompileStatic etc.) you don't have to
write everything dynamic anyway.


On Tue, Feb 21, 2017 at 10:51 PM, Raviteja Lokineni <> wrote:

> Hi Devs,
> I was trying to pitch using Grails for one of our projects and the
> discussions always ended up with "using reflections in JVM is slow period".
> I am not knowledgeable to defend the internals of either Groovy or Grails,
> need some help on this topic.
> The only selling point that they identified was GORM.
> I thought this might be the time to ask the developer community. I am
> trying to gather some points on using Grails over a Spring boot application.
> Also, can anyone help me understand how Groovy runtime optimizations are
> applied on a high level and if it will affect the runtime performance.
> Thanks,
> --
> *Raviteja Lokineni* | Business Intelligence Developer
> TD Ameritrade
> E:
> [image: View Raviteja Lokineni's profile on LinkedIn]
> <>
> --
> You received this message because you are subscribed to the Google Groups
> "Grails Dev Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
> To post to this group, send email to
> To view this discussion on the web visit
> msgid/grails-dev-discuss/CAJpE9rUp8B84w6Mz7k4_zw6c2EMh4W08oe%3Dsc_xsqfJi%
> <>
> .
> For more options, visit

Graeme Rocher

View raw message