Alternatives to Vaadin logo

Alternatives to Vaadin

Play, Spring MVC, AngularJS, JavaFX, and GWT are the most popular alternatives and competitors to Vaadin.
157
221
+ 1
34

What is Vaadin and what are its top alternatives?

It is the fastest way to build web applications in Java. It automates the communication between your server and the browser and gives you a high-level component API for all Vaadin components
Vaadin is a tool in the Frameworks (Full Stack) category of a tech stack.
Vaadin is an open source tool with 366 GitHub stars and 60 GitHub forks. Here’s a link to Vaadin's open source repository on GitHub

Top Alternatives to Vaadin

  • Play
    Play

    Play Framework makes it easy to build web applications with Java & Scala. Play is based on a lightweight, stateless, web-friendly architecture. Built on Akka, Play provides predictable and minimal resource consumption (CPU, memory, threads) for highly-scalable applications. ...

  • Spring MVC
    Spring MVC

    A Java framework that follows the Model-View-Controller design pattern and provides an elegant solution to use MVC in spring framework by the help of DispatcherServlet. ...

  • AngularJS
    AngularJS

    AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding. ...

  • JavaFX
    JavaFX

    It is a set of graphics and media packages that enables developers to design, create, test, debug, and deploy rich client applications that operate consistently across diverse platforms. ...

  • GWT
    GWT

    It is a development toolkit for building and optimizing complex browser-based applications. Its goal is to enable productive development of high-performance web applications without the developer having to be an expert in browser quirks, XMLHttpRequest, and JavaScript. ...

  • PrimeFaces
    PrimeFaces

    It is a popular open source framework for JavaServer Faces featuring over 100 components, touch optimized mobilekit, client side validation, theme engine and more. ...

  • React
    React

    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...

  • JSF
    JSF

    It is used for building component-based user interfaces for web applications and was formalized as a standard through the Java Community ...

Vaadin alternatives & related posts

Play logo

Play

707
542
495
The High Velocity Web Framework For Java and Scala
707
542
+ 1
495
PROS OF PLAY
  • 81
    Scala
  • 55
    Built on akka
  • 55
    Web-friendly architecture
  • 50
    Stateless
  • 47
    High-scalable
  • 46
    Fast
  • 40
    Open source
  • 34
    Java
  • 27
    High velocity
  • 24
    Fun
  • 9
    Lightweight
  • 8
    Non-blocking io
  • 5
    Developer friendly
  • 5
    Simple template engine
  • 4
    Scalability
  • 3
    Pure love
  • 2
    Resource efficient
CONS OF PLAY
  • 3
    Evolves fast, keep up with releases
  • 1
    Unnecessarily complicated

related Play posts

Alex A

Some may wonder why did we choose Grails ? Really good question :) We spent quite some time to evaluate what framework to go with and the battle was between Play Scala and Grails ( Groovy ). We have enough experience with both and, to be honest, I absolutely in love with Scala; however, the tipping point for us was the potential speed of development. Grails allows much faster development pace than Play , and as of right now this is the most important parameter. We might convert later though. Also, worth mentioning, by default Grails comes with Gradle as a build tool, so why change?

See more
Spring MVC logo

Spring MVC

441
452
0
A Java framework which is used to build web applications
441
452
+ 1
0
PROS OF SPRING MVC
    Be the first to leave a pro
    CONS OF SPRING MVC
      Be the first to leave a con

      related Spring MVC posts

      NIDHISH PUTHIYADATH
      Lead Software Engineer at EDIFECS · | 1 upvote · 139.3K views

      Material Design for Angular Angular 2 Node.js TypeScript Spring-Boot RxJS Microsoft SQL Server Hibernate Spring MVC

      We built our customer facing portal application using Angular frontend backed by Spring boot.

      See more
      AngularJS logo

      AngularJS

      49.2K
      36K
      5.2K
      Superheroic JavaScript MVW Framework
      49.2K
      36K
      + 1
      5.2K
      PROS OF ANGULARJS
      • 887
        Quick to develop
      • 587
        Great mvc
      • 572
        Powerful
      • 521
        Restful
      • 503
        Backed by google
      • 349
        Two-way data binding
      • 343
        Javascript
      • 328
        Open source
      • 305
        Dependency injection
      • 197
        Readable
      • 75
        Fast
      • 64
        Directives
      • 63
        Great community
      • 56
        Free
      • 38
        Extend html vocabulary
      • 29
        Components
      • 26
        Easy to test
      • 24
        Easy to learn
      • 23
        Easy to templates
      • 23
        Great documentation
      • 21
        Easy to start
      • 18
        Awesome
      • 17
        Light weight
      • 14
        Angular 2.0
      • 14
        Javascript mvw framework
      • 13
        Great extensions
      • 13
        Efficient
      • 10
        Easy to prototype with
      • 8
        High performance
      • 8
        Coffeescript
      • 7
        Mvc
      • 7
        Two-way binding
      • 7
        Lots of community modules
      • 6
        Easy to e2e
      • 6
        Clean and keeps code readable
      • 5
        Easy for small applications
      • 5
        One of the best frameworks
      • 4
        Fast development
      • 4
        Works great with jquery
      • 3
        I do not touch DOM
      • 2
        Be a developer, not a plumber.
      • 2
        Declarative programming
      • 2
        Dart
      • 2
        Community
      • 2
        The two-way Data Binding is awesome
      • 2
        Hierarchical Data Structure
      • 2
        Typescript
      • 1
        Botionescu@gmail.com
      • 1
        The powerful of binding, routing and controlling routes
      • 1
        Fkin awesome
      • 1
        Opinionated in the right areas
      • 1
        Supports api , easy development
      • 1
        Common Place
      • 1
        Great
      • 1
        Very very useful and fast framework for development
      • 1
        Amazing community support
      • 1
        Readable code
      • 1
        Linear learning curve
      • 1
        Scopes
      • 1
        Programming fun again
      • 1
        Acoperișul
      • 1
        Consistency with backend architecture if using Nest
      • 0
        Httpș//Acoperișul 0757604335
      • 0
        Angular js
      • 0
        Oautho loc
      • 0
        Shvzjn
      • 0
        Acoperișul 0757604335
      • 0
        Js
      • 0
        Bot Ionescu
      • 0
        Google.com
      CONS OF ANGULARJS
      • 10
        Complex
      • 3
        Dependency injection
      • 2
        Learning Curve
      • 2
        Event Listener Overload
      • 1
        Hard to learn

      related AngularJS posts

      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2.5M views

      Our whole Node.js backend stack consists of the following tools:

      • Lerna as a tool for multi package and multi repository management
      • npm as package manager
      • NestJS as Node.js framework
      • TypeScript as programming language
      • ExpressJS as web server
      • Swagger UI for visualizing and interacting with the API’s resources
      • Postman as a tool for API development
      • TypeORM as object relational mapping layer
      • JSON Web Token for access token management

      The main reason we have chosen Node.js over PHP is related to the following artifacts:

      • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
      • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
      • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
      • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
      See more
      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 22 upvotes · 1.2M views

      Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

      • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
      • Vue Styleguidist as our style guide and pool of developed Vue.js components
      • Vuetify as Material Component Framework (for fast app development)
      • TypeScript as programming language
      • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
      • ESLint, TSLint and Prettier for coding style and code analyzes
      • Jest as testing framework
      • Google Fonts and Font Awesome for typography and icon toolkit
      • NativeScript-Vue for mobile development

      The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

      • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
      • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
      • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
      • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
      • Large scaling. Vue.js can help to develop pretty large reusable templates.
      • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
      See more
      JavaFX logo

      JavaFX

      236
      323
      9
      A Java library for building Rich Internet Applications
      236
      323
      + 1
      9
      PROS OF JAVAFX
      • 9
        Light
      CONS OF JAVAFX
      • 1
        Community support less than qt
      • 1
        Complicated

      related JavaFX posts

      GWT logo

      GWT

      79
      78
      0
      An open-source set of tools to create and maintain complex JavaScript front-end applications
      79
      78
      + 1
      0
      PROS OF GWT
        Be the first to leave a pro
        CONS OF GWT
          Be the first to leave a con

          related GWT posts

          PrimeFaces logo

          PrimeFaces

          88
          142
          3
          An open-source user interface component library
          88
          142
          + 1
          3
          PROS OF PRIMEFACES
          • 1
            JEE Integration
          • 1
            Support Contract available
          • 1
            Nice Components
          CONS OF PRIMEFACES
          • 1
            Some components have to be bought
          • 1
            JSF

          related PrimeFaces posts

          I need to modernize a Java web application that runs on JSF. I am used to building websites, so Bootstrap kinda feels like "home." But when it comes to applications, I feel Bootstrap is not the right way to go. Can someone explain to me what PrimeFaces is capable of in comparison with BS?

          See more
          React logo

          React

          128.4K
          104.8K
          3.8K
          A JavaScript library for building user interfaces
          128.4K
          104.8K
          + 1
          3.8K
          PROS OF REACT
          • 774
            Components
          • 657
            Virtual dom
          • 567
            Performance
          • 491
            Simplicity
          • 438
            Composable
          • 176
            Data flow
          • 162
            Declarative
          • 124
            Isn't an mvc framework
          • 114
            Reactive updates
          • 111
            Explicit app state
          • 39
            JSX
          • 23
            Learn once, write everywhere
          • 19
            Uni-directional data flow
          • 17
            Easy to Use
          • 14
            Works great with Flux Architecture
          • 10
            Great perfomance
          • 8
            Built by Facebook
          • 7
            Javascript
          • 5
            Speed
          • 5
            TypeScript support
          • 4
            Feels like the 90s
          • 4
            Hooks
          • 4
            Awesome
          • 4
            Scalable
          • 4
            Easy to start
          • 3
            Server Side Rendering
          • 3
            Fancy third party tools
          • 3
            Props
          • 3
            Obama
          • 3
            Server side views
          • 3
            Functional
          • 3
            Scales super well
          • 3
            Excellent Documentation
          • 3
            Cross-platform
          • 2
            Rich ecosystem
          • 2
            Start simple
          • 2
            Allows creating single page applications
          • 2
            Sdfsdfsdf
          • 2
            Beautiful and Neat Component Management
          • 2
            Very gentle learning curve
          • 2
            Has functional components
          • 2
            Simple
          • 2
            Closer to standard JavaScript and HTML than others
          • 2
            Super easy
          • 2
            Has arrow functions
          • 2
            Strong Community
          • 2
            Great migration pathway for older systems
          • 2
            SSR
          • 2
            Fast evolving
          • 2
            Simple, easy to reason about and makes you productive
          • 2
            Just the View of MVC
          • 1
            Sharable
          • 1
            Every decision architecture wise makes sense
          • 1
            Permissively-licensed
          • 1
            Split your UI into components with one true state
          • 1
            Fragments
          • 0
            Recharts
          CONS OF REACT
          • 36
            Requires discipline to keep architecture organized
          • 23
            No predefined way to structure your app
          • 22
            Need to be familiar with lots of third party packages
          • 9
            JSX
          • 7
            Not enterprise friendly
          • 5
            One-way binding only
          • 2
            State consistency with backend neglected
          • 2
            Bad Documentation
          • 1
            Paradigms change too fast

          related React posts

          Vaibhav Taunk
          Team Lead at Technovert · | 31 upvotes · 1.9M views

          I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

          See more
          Adebayo Akinlaja
          Engineering Manager at Andela · | 27 upvotes · 1.1M views

          I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

          A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

          In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

          If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

          See more
          JSF logo

          JSF

          118
          188
          4
          It is used for building component-based web interfaces
          118
          188
          + 1
          4
          PROS OF JSF
          • 2
            Rich and comprehensive Request Life-cycle
          • 1
            Very Mature UI framework
          • 1
            Server Side component
          CONS OF JSF
            Be the first to leave a con

            related JSF posts

            Hello guys! I would ask for your advice. Our situation is like that there will be a project to revamp workflows and introduce new services like mobile apps, machine learning, and some online services that would use cloud storage. We use JSF, JavaScript, Ajax, Spring, Oracle 12c running on Linux (VM) and providing online services to internal users and the public. But, we are not technically savvy enough to evaluate what tools should be introduced. Personally, I am evaluating whether to take this opportunity to change our practice/PM approach from Prince to Scrum/Agile (It seemed that DevOps is popular) ... Since we adopt ISO 27001 and ISO 20000, security is a crucial factor that we consider. Would you please help to recommend a list of tools and explain the reasons why you recommend them? Thanks in advance~!

            See more

            I need to modernize a Java web application that runs on JSF. I am used to building websites, so Bootstrap kinda feels like "home." But when it comes to applications, I feel Bootstrap is not the right way to go. Can someone explain to me what PrimeFaces is capable of in comparison with BS?

            See more