Why I Prefer Grails For Rapid Scaffolding of New Apps

There are many good frameworks out there, but the one I prefer for quick demos, simple applications and rapid scaffolding is Grails. Why? Simply put – with just a few lines of code you have a fully functional application: user interface, controllers, data validation and persistence.

But Grails is much more than a tool for quick prototypes. It is a fully featured platform based on the rock solid foundation of Spring, Hibernate and other enterprise-grade frameworks. Plug-ins can be added any time and they will seamlessly add new features to the application.

Grails uses Groovy as its primary programming language, but as it runs on the Java Virtual Machine, you have full access and interoperatbility with any existing Java library. Tooling support is also excellent, both from command line and from IDEs like Eclipse or IntelliJ IDEA.

If you think that the above paragraphs are just hyperboles from an enthusiast fanboy, continue reading and experiment for yourself how easy is to build a new app from scratch.

Continue reading “Why I Prefer Grails For Rapid Scaffolding of New Apps”

Advertisements

Maturing the Continuous Delivery Pipeline

A bit old but a good read anyway!

DevOpsGuys

The Maturity Model is a useful assessment tool for understanding your organizations level of Continuous Delivery adoption. Many organizations today have achieved what is needed to move from Level-1 (Regressive) to Level-0 (Repeatable), which is a significant accomplishment and as a reader of this blog post, you’re either about to start your journey of improvement or are already underway.

Continuous Delivery Maturity Model Continuous Delivery Maturity Model

The Maturity Model

The advice for organizations wanting to adopt Continuous Delivery is ever more abundant, but for organizations that started adoption some time ago, the guidance on how to mature the process is still sparse. In this article, we explore one continuous improvement methodology that may help your organization mature its’ Continuous Delivery process.

Humble and Farley outline maturity Level 0 (Repeatable) – as one having process which is documented and partly automated.1 For this to be true, an organization must have first classified its’ software delivery maturity, identified…

View original post 1,592 more words