|Vaadin Reaches Version 21|
|Written by Nikos Vaggalis|
|Thursday, 16 September 2021|
The versatile full stack Java-based framework that is a competitor to Spring MVC, continues to innovate with its new release of v21. But first, what exactly is Vaadin?
The issue is more prevalent in an Enterprise setting where you've got a pool of Java dinosaurs, err developers, who are great at defining the business logic and building solid applications, but when it comes to the Web and the front-end they lose their sleep over. This is also depicted in Vaadin's adoption - of 4% according to Snyk's JVM Ecosystem Report 2021 and only 2% according to Jetbrain's State of Java report 2021.
But that 2 to 4% represents the 40% of the Fortune 500. Companies known to use Vaadin today include: Disney, Wells Fargo, Bank of America, GlaxoSmithKline, Raytheon, JP Morgan Chase, Volkswagen America, Rockwell Automation, National Public Radio (NPR) and many more.
As such, frameworks that hide this complexity and make use of a single language for writing both the back end and the front end have been on the rise. We've discovered .NET's side of the story in the article "Blazor WebAssembly Crash Course", where I found that
In any case you just don't have to think about Server side or Client side; you just go on developing in your favorite Java like you used to do and let the framework handle both sides of the equation.
In addition Vaadin requires less configuration than a Spring MVC project to start with. However they are not mutually exclusive, they can also work together. Check "Using Vaadin with Spring MVC" for more. Of course, both go together with Spring Boot.
So is server side Flow the answer to all problems? Vaadin's latest versions have introduced yet another way of building the front-end, that of Fusion. In an attempt to lure developers that work say with Angular, Fusion allows to do your actual reactive UI logic in TypeScript while continuing writing the backend in Java.
With all that background setting to provide the context out of the way, let's now concentrate on what release 21 brings:
The project's roadmap reveals that it is very much alive with a vibrant and supportive ecosystem around it. On that roadmap there's some interesting todos outstanding, but the one that merits attention is Stateless Fusion. Vaadin Flow uses server side sessions heavily and Fusion does the same. This change would mean that Fusion would not create or store information into server sessions, allowing easier horizontal scaling of instances and high availability of services.
So given all the above it's up to you to decide whether setting Spring MVC aside, even for a brief moment, in order to give Vaadin a try is worth it. And to make that transition easier there's a brand new book out on Apress by Alejandro Duarte of the Vaadin team, Practical Vaadin: Developing Web Applications with Java.
or email your comment to: firstname.lastname@example.org
|Last Updated ( Thursday, 16 September 2021 )|