Alternatives to Apache Wicket logo

Alternatives to Apache Wicket

Spring MVC, Vaadin, AngularJS, Spring, and Django are the most popular alternatives and competitors to Apache Wicket.
54
39
+ 1
2

What is Apache Wicket and what are its top alternatives?

It is a component-based web application framework for the Java programming language conceptually similar to JavaServer Faces and Tapestry.
Apache Wicket is a tool in the Frameworks (Full Stack) category of a tech stack.

Top Alternatives to Apache Wicket

  • 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. ...

  • Vaadin

    Vaadin

    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 ...

  • 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. ...

  • Spring

    Spring

    A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments. ...

  • Django

    Django

    Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. ...

  • 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 ...

  • Spring Boot

    Spring Boot

    Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration. ...

Apache Wicket alternatives & related posts

Spring MVC logo

Spring MVC

423
419
0
A Java framework which is used to build web applications
423
419
+ 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 · 130.1K 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
      Vaadin logo

      Vaadin

      142
      196
      33
      Components and tools for building web apps in Java
      142
      196
      + 1
      33
      PROS OF VAADIN
      • 8
        Java
      • 6
        Open Source
      • 6
        Compatibility
      • 5
        Components
      • 3
        Performance
      • 2
        Abstraction
      • 2
        Example packages
      • 1
        OSGI Support
      CONS OF VAADIN
      • 3
        Paid for more features

      related Vaadin posts

      AngularJS logo

      AngularJS

      45.2K
      32.9K
      5.2K
      Superheroic JavaScript MVW Framework
      45.2K
      32.9K
      + 1
      5.2K
      PROS OF ANGULARJS
      • 887
        Quick to develop
      • 587
        Great mvc
      • 571
        Powerful
      • 521
        Restful
      • 503
        Backed by google
      • 348
        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
        Great documentation
      • 23
        Easy to templates
      • 21
        Easy to start
      • 17
        Light weight
      • 17
        Awesome
      • 14
        Javascript mvw framework
      • 14
        Angular 2.0
      • 13
        Great extensions
      • 13
        Efficient
      • 10
        Easy to prototype with
      • 8
        Coffeescript
      • 8
        High performance
      • 7
        Lots of community modules
      • 7
        Two-way binding
      • 7
        Mvc
      • 6
        Clean and keeps code readable
      • 6
        Easy to e2e
      • 5
        One of the best frameworks
      • 5
        Easy for small applications
      • 4
        Works great with jquery
      • 4
        Fast development
      • 2
        Be a developer, not a plumber.
      • 2
        Hierarchical Data Structure
      • 2
        I do not touch DOM
      • 2
        The two-way Data Binding is awesome
      • 2
        Dart
      • 2
        Typescript
      • 2
        Community
      • 2
        Declarative programming
      • 1
        Programming fun again
      • 1
        Acoperișul
      • 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
      • 0
        Httpș//Acoperișul 0757604335
      • 0
        Google.com
      • 0
        Bot Ionescu
      • 0
        Angular js
      • 0
        Js
      • 0
        Oautho loc
      • 0
        Shvzjn
      • 0
        Acoperișul 0757604335
      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.1M 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 · | 20 upvotes · 817.7K 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
      Spring logo

      Spring

      3.3K
      3.9K
      1K
      Provides a comprehensive programming and configuration model for modern Java-based enterprise applications
      3.3K
      3.9K
      + 1
      1K
      PROS OF SPRING
      • 220
        Java
      • 154
        Open source
      • 132
        Great community
      • 119
        Very powerful
      • 111
        Enterprise
      • 62
        Lot of great subprojects
      • 58
        Easy setup
      • 44
        Convention , configuration, done
      • 37
        Standard
      • 29
        Love the logic
      • 11
        Good documentation
      • 10
        Dependency injection
      • 9
        Stability
      • 6
        MVC
      • 6
        Easy
      • 3
        Strong typing
      • 3
        Makes the hard stuff fun & the easy stuff automatic
      • 2
        Code maintenance
      • 2
        Best practices
      • 2
        Maven
      • 2
        Great Desgin
      • 2
        Easy Integration with Spring Security
      • 2
        Integrations with most other Java frameworks
      • 1
        Java has more support and more libraries
      • 1
        Supports vast databases
      • 1
        Large ecosystem with seamless integration
      • 1
        OracleDb integration
      • 1
        Live project
      CONS OF SPRING
      • 15
        Draws you into its own ecosystem and bloat
      • 3
        Verbose configuration
      • 3
        Poor documentation
      • 3
        Java
      • 1
        Java is more verbose language in compare to python

      related Spring posts

      Is learning Spring and Spring Boot for web apps back-end development is still relevant in 2021? Feel free to share your views with comparison to Django/Node.js/ ExpressJS or other frameworks.

      Please share some good beginner resources to start learning about spring/spring boot framework to build the web apps.

      See more

      I am consulting for a company that wants to move its current CubeCart e-commerce site to another PHP based platform like PrestaShop or Magento. I was interested in alternatives that utilize Node.js as the primary platform. I currently don't know PHP, but I have done full stack dev with Java, Spring, Thymeleaf, etc.. I am just unsure that learning a set of technologies not commonly used makes sense. For example, in PrestaShop, I would need to work with JavaScript better and learn PHP, Twig, and Bootstrap. It seems more cumbersome than a Node JS system, where the language syntax stays the same for the full stack. I am looking for thoughts and advice on the relevance of PHP skillset into the future AND whether the Node based e-commerce open source options can compete with Magento or Prestashop.

      See more
      Django logo

      Django

      26.8K
      23.7K
      3.8K
      The Web framework for perfectionists with deadlines
      26.8K
      23.7K
      + 1
      3.8K
      PROS OF DJANGO
      • 634
        Rapid development
      • 468
        Open source
      • 401
        Great community
      • 353
        Easy to learn
      • 263
        Mvc
      • 215
        Beautiful code
      • 210
        Elegant
      • 193
        Free
      • 191
        Great packages
      • 178
        Great libraries
      • 68
        Restful
      • 65
        Comes with auth and crud admin panel
      • 65
        Powerful
      • 60
        Great documentation
      • 58
        Great for web
      • 44
        Python
      • 37
        Great orm
      • 34
        Great for api
      • 27
        All included
      • 22
        Web Apps
      • 21
        Fast
      • 18
        Used by top startups
      • 16
        Clean
      • 15
        Easy setup
      • 15
        Sexy
      • 12
        Convention over configuration
      • 10
        ORM
      • 9
        The Django community
      • 9
        Allows for very rapid development with great libraries
      • 6
        Great MVC and templating engine
      • 6
        King of backend world
      • 6
        Its elegant and practical
      • 5
        Mvt
      • 5
        Batteries included
      • 5
        Full stack
      • 5
        Fast prototyping
      • 5
        Easy Structure , useful inbuilt library
      • 5
        Easy to develop end to end AI Models
      • 5
        Have not found anything that it can't do
      • 4
        Very quick to get something up and running
      • 4
        Easy to use
      • 4
        Easy
      • 4
        Cross-Platform
      • 3
        Map
      • 3
        Great peformance
      • 3
        Scaffold
      • 3
        Just the right level of abstraction
      • 3
        Modular
      • 3
        Full-Text Search
      • 3
        Zero code burden to change databases
      • 3
        Python community
      • 3
        Many libraries
      • 2
        Easy to change database manager
      • 1
        Node js
      CONS OF DJANGO
      • 25
        Underpowered templating
      • 19
        Underpowered ORM
      • 19
        Autoreload restarts whole server
      • 15
        URL dispatcher ignores HTTP method
      • 10
        Internal subcomponents coupling
      • 7
        Admin
      • 7
        Not nodejs
      • 6
        Configuration hell
      • 4
        Not as clean and nice documentation like Laravel
      • 3
        Python
      • 3
        Not typed
      • 3
        Bloated admin panel included
      • 2
        Overwhelming folder structure
      • 1
        InEffective Multithreading

      related Django posts

      Dmitry Mukhin

      Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.

      Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.

      For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.

      However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.

      All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.

      See more

      Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?

      See more
      React logo

      React

      113K
      91.7K
      3.8K
      A JavaScript library for building user interfaces
      113K
      91.7K
      + 1
      3.8K
      PROS OF REACT
      • 760
        Components
      • 652
        Virtual dom
      • 563
        Performance
      • 486
        Simplicity
      • 436
        Composable
      • 175
        Data flow
      • 159
        Declarative
      • 124
        Isn't an mvc framework
      • 113
        Reactive updates
      • 111
        Explicit app state
      • 32
        JSX
      • 23
        Learn once, write everywhere
      • 19
        Uni-directional data flow
      • 16
        Easy to Use
      • 14
        Works great with Flux Architecture
      • 10
        Great perfomance
      • 8
        Built by Facebook
      • 7
        Javascript
      • 5
        TypeScript support
      • 5
        Speed
      • 4
        Feels like the 90s
      • 4
        Scalable
      • 4
        Easy to start
      • 4
        Awesome
      • 3
        Fancy third party tools
      • 3
        Hooks
      • 3
        Functional
      • 3
        Server side views
      • 3
        Props
      • 2
        Rich ecosystem
      • 2
        Obama
      • 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
        Excellent Documentation
      • 2
        Scales super well
      • 2
        Just the View of MVC
      • 2
        Server Side Rendering
      • 2
        Cross-platform
      • 1
        Fragments
      • 1
        Start simple
      • 1
        Every decision architecture wise makes sense
      • 1
        Permissively-licensed
      • 1
        Beautiful and Neat Component Management
      • 1
        Sdfsdfsdf
      • 1
        Allows creating single page applications
      • 1
        Split your UI into components with one true state
      • 1
        Sharable
      CONS OF REACT
      • 35
        Requires discipline to keep architecture organized
      • 23
        No predefined way to structure your app
      • 21
        Need to be familiar with lots of third party packages
      • 8
        JSX
      • 7
        Not enterprise friendly
      • 4
        One-way binding only
      • 2
        State consistency with backend neglected
      • 2
        Bad Documentation

      related React posts

      Vaibhav Taunk
      Team Lead at Technovert · | 31 upvotes · 1.7M 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 · | 26 upvotes · 795.6K 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

      110
      160
      4
      It is used for building component-based web interfaces
      110
      160
      + 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
        Spring Boot logo

        Spring Boot

        17.2K
        15.2K
        914
        Create Spring-powered, production-grade applications and services with absolute minimum fuss
        17.2K
        15.2K
        + 1
        914
        PROS OF SPRING BOOT
        • 135
          Powerful and handy
        • 127
          Easy setup
        • 118
          Java
        • 86
          Spring
        • 82
          Fast
        • 42
          Extensible
        • 34
          Lots of "off the shelf" functionalities
        • 29
          Cloud Solid
        • 23
          Caches well
        • 21
          Many receipes around for obscure features
        • 20
          Productive
        • 20
          Modular
        • 19
          Integrations with most other Java frameworks
        • 19
          Spring ecosystem is great
        • 18
          Fast Performance With Microservices
        • 17
          Auto-configuration
        • 16
          Community
        • 13
          Easy setup, Community Support, Solid for ERP apps
        • 13
          One-stop shop
        • 12
          Cross-platform
        • 12
          Easy to parallelize
        • 11
          Easy setup, good for build erp systems, well documented
        • 11
          Powerful 3rd party libraries and frameworks
        • 10
          Easy setup, Git Integration
        • 3
          It's so easier to start a project on spring
        • 3
          Kotlin
        CONS OF SPRING BOOT
        • 19
          Heavy weight
        • 17
          Annotation ceremony
        • 10
          Many config files needed
        • 8
          Java
        • 5
          Reactive
        • 4
          Excellent tools for cloud hosting, since 5.x

        related Spring Boot posts

        Is learning Spring and Spring Boot for web apps back-end development is still relevant in 2021? Feel free to share your views with comparison to Django/Node.js/ ExpressJS or other frameworks.

        Please share some good beginner resources to start learning about spring/spring boot framework to build the web apps.

        See more
        Praveen Mooli
        Engineering Manager at Taylor and Francis · | 14 upvotes · 2M views

        We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

        To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

        To build #Webapps we decided to use Angular 2 with RxJS

        #Devops - GitHub , Travis CI , Terraform , Docker , Serverless

        See more