我的书签
添加书签
移除书签Migration Strategies
For any existing Vaadin 8 or 7 application, it might be desirable to extend the lifetime of the application and make it possible to add new features using Vaadin 14. There are several migration strategies to consider as the need for migration is always application and business specific.
Note that in case of choosing to migrate, it is recommended to go to the latest LTS version, which currently is Vaadin 14.
Use Vaadin Eight - It Is Great!
You can stay with Vaadin 8. We are going to maintain it at least until 2022. That gives you the option to plan your migration longer term, and consider what is the needed lifetime for your application. You should look at the needs of your users and how those needs and the technologies used evolve during that time.
Internet Explorer 11 support is still a critical thing for many applications, and for IE11 Vaadin 8 might offer better performance than Vaadin platform since polyfills are needed with IE 11. During the guaranteed lifetime of Vaadin 8, the usage of IE11 should decrease significantly from what it is now.
During the remaining years of Vaadin 8 support, both the quarterly Vaadin platform releases and the minor releases for Vaadin 14 will bring more and more features that you can start using when you eventually decide to migrate to the latest Vaadin LTS version (currently 14) or start building a new application with a fresh design.
Using the Multiplatform Runtime for Running V8 Application Inside V14
Multiplatform Runtime makes it possible to run views and components from your Vaadin 7 and 8 applications inside Vaadin 14. This helps you migrate it to version 14 bit by bit, or just incrementally add V10 features while also including existing application features as-is.
Using the runtime, you will be able to get your V7 or V8 applications running inside a Vaadin 14 application after a couple of quick steps. Then you can migrate the necessary parts while having a working application after each step.
Multiplatform runtime is part of the platform and has LTS support for using it with Vaadin 14. See the Multiplatform Runtime documentation for more information.
Transform an Existing Application To Vaadin 14
Transforming a Vaadin 8 app to Vaadin 14 by reusing backend interaction, business logic, and as much as possible of UI logic, but updating the UI to use brand new components. When planning this migration, you should at a minimum read through all of this documentation to understand the differences and verify what features are available and what you need to redesign. One big benefit is that the Data APIs, Binder and DataProvider, work the same way in V14, so you won’t have to rework your backend integration.
Fresh Start by Redesigning Application for Vaadin 14
Sometimes the best approach is to make a fresh start - this way you will be able to focus on using new V14 features to deliver value to your users, instead of carrying over legacy code. As mentioned in previous topics, there is still probably some opportunities to reuse existing solutions related to integration to your business logic and backend.
Migration Assessment Service
To help you understand what a migration to Vaadin 14 means to you, Vaadin offers an assessment service led by Vaadin experts. During the assessment, our experts will gain an understanding of your organization’s objectives and concerns, and analyze your application code. Read more about the service.
You can contact us to get us to migrate the application for you.
