Hello Grails Team,

I wanted to start a discussion to better understand how Grails is currently
being used in real-world applications, especially from the perspective of
developers who are new to the framework.

Grails provides a very productive development experience with its
convention-over-configuration approach and strong integration with the
Spring ecosystem. From a learning and adoption perspective, it would be
helpful to understand which architectural patterns are most commonly
followed when building applications with Grails today.

For example, in practice, do most teams use Grails primarily for the
following:
• traditional MVC-based web applications
• API-first backend services
• microservice-oriented architectures
• Grails as a backend integrated with frontend frameworks like React or Vue

Additionally, when developers start learning Grails, would it be more
useful to see complete real-world flows such as:
• building REST APIs using Grails
• authentication and authorization implementation
• integration between Grails backend and modern frontend frameworks
• deployment-oriented examples

Understanding which real-world scenarios are most relevant could help
ensure learning resources align with current development practices and
improve the onboarding experience for new Grails developers.

I would really appreciate hearing the community’s thoughts on which
practical use cases best represent how Grails is used today.

Thank you for your insights.

Reply via email to