Grails and Rails are great at some thing like scaffolding. Spring Boot has no such feature. But in my experience, you never keep scaffolding around long before reworking it into your own look-and-feel. So while scaffolding is neat and makes for quick demos, it's mostly throwaway code.
But Spring Boot and Spring have some other similarities with Grails and Rails. A few things come immediately to mind:
First, Grails (as of Grails 3) *is* Spring Boot. Grails is built on top of Spring Boot, so if you're developing a Grails 3 app, you are indirectly also developing a Boot app!
The getting started experience with Boot is not exactly like, but not entirely unlike that of Grails/Rails. Specifically, if you use the Initializr (and who wouldn't?), whether by going to start.spring.io or using it via your IDE, you can get up and running with Spring Boot in no time.
Finally, Spring Data's automagic repositories are quite similar to GORM from Grails. GORM, being based on Groovy, has a slight advantage by being able to leverage Groovy metaprogramming for some of its magic, but Spring Data repositories (which don't have the luxury of being able to rely on Groovy) are still quite comparable to GORM repositories.
I've done a little work with Rails and Grails in my past and can't say that there's anything about either of them that I miss when I work with Spring Boot.
Carl Byrd wrote:Hi Craig,
I've never used Spring or Sprint Boot, but I have Grails experience. Is any part of Spring similar to other server side MVC frameworks like Grails, Rails, etc as far as initial setup and convention?