In the last part of the Grails vs. CUBA series, it is all about the remaining parts like Testing as well as the ecosystem. After covering the last parts of the comparison there will be a summary.
After comparing Grails and CUBA mostly from a persistence and business logic perspective in the first blog post, this time I’ll take a look at the frontend as well as at cross cutting concerns like security.
Since I started a transition from Grails to CUBA some time ago, I thought it would be a good idea to give you a technical comparison between those two frameworks. In this blog post series I go though different aspects, starting with data access and business logic in this post, to conclude why I finally decided to give CUBA a shot in more and more of my projects.
Views are a concept of CUBA that is not that widespread in the web framework world, and to understand it means to prevent running into weird issues around not-loaded data and applications that therefore stop working. Let’s look at the idea behind views and why they are actually pretty neat.
Doing diagnosis on running applications is oftentimes a very tedious thing. To make this experience as smooth as possible, lets look on how CUBA can help us here. After that we will take a look at extended features that we can use like an interactive groovy console.