Alternatives to Apache Struts logo

Alternatives to Apache Struts

Apache Tomcat, Spring MVC, Spring, Spring Boot, and AngularJS are the most popular alternatives and competitors to Apache Struts.
48
29
+ 1
0

What is Apache Struts and what are its top alternatives?

It is a free, open-source, MVC framework for creating elegant, modern Java web applications. It favors convention over configuration, is extensible using a plugin architecture, and ships with plugins to support REST, AJAX and JSON.
Apache Struts is a tool in the Frameworks (Full Stack) category of a tech stack.
Apache Struts is an open source tool with 1.1K GitHub stars and 716 GitHub forks. Here’s a link to Apache Struts's open source repository on GitHub

Top Alternatives to Apache Struts

  • Apache Tomcat

    Apache Tomcat

    Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations. ...

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

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

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

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

  • JBoss

    JBoss

    An application platform for hosting your apps that provides an innovative modular, cloud-ready architecture, powerful management and automation, and world class developer productivity. ...

  • Node.js

    Node.js

    Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices. ...

  • Django

    Django

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

Apache Struts alternatives & related posts

Apache Tomcat logo

Apache Tomcat

11.3K
7.8K
200
An open source software implementation of the Java Servlet and JavaServer Pages technologies
11.3K
7.8K
+ 1
200
PROS OF APACHE TOMCAT
  • 79
    Easy
  • 72
    Java
  • 48
    Popular
  • 1
    Spring web
CONS OF APACHE TOMCAT
    Be the first to leave a con

    related Apache Tomcat posts

    Остап Комплікевич

    I need some advice to choose an engine for generation web pages from the Spring Boot app. Which technology is the best solution today? 1) JSP + JSTL 2) Apache FreeMarker 3) Thymeleaf Or you can suggest even other perspective tools. I am using Spring Boot, Spring Web, Spring Data, Spring Security, PostgreSQL, Apache Tomcat in my project. I have already tried to generate pages using jsp, jstl, and it went well. However, I had huge problems via carrying already created static pages, to jsp format, because of syntax. Thanks.

    See more

    Java Spring JUnit

    Apache HTTP Server Apache Tomcat

    MySQL

    See more
    Spring MVC logo

    Spring MVC

    388
    379
    0
    A Java framework which is used to build web applications
    388
    379
    + 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 · 122K 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
        Spring logo

        Spring

        3.1K
        3.6K
        1K
        Provides a comprehensive programming and configuration model for modern Java-based enterprise applications
        3.1K
        3.6K
        + 1
        1K
        PROS OF SPRING
        • 219
          Java
        • 153
          Open source
        • 131
          Great community
        • 118
          Very powerful
        • 110
          Enterprise
        • 61
          Lot of great subprojects
        • 58
          Easy setup
        • 44
          Convention , configuration, done
        • 37
          Standard
        • 29
          Love the logic
        • 10
          Dependency injection
        • 10
          Good documentation
        • 9
          Stability
        • 6
          Easy
        • 6
          MVC
        • 3
          Makes the hard stuff fun & the easy stuff automatic
        • 3
          Strong typing
        • 2
          Great Desgin
        • 2
          Maven
        • 2
          Easy Integration with Spring Security
        • 2
          Integrations with most other Java frameworks
        • 1
          Live project
        • 1
          Supports vast databases
        • 1
          Best practices
        • 1
          Large ecosystem with seamless integration
        • 1
          Java has more support and more libraries
        • 1
          Code maintenance
        • 1
          OracleDb integration
        CONS OF SPRING
        • 13
          Draws you into its own ecosystem and bloat
        • 2
          Verbose configuration
        • 2
          Poor documentation
        • 1
          Java

        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
        Spring Boot logo

        Spring Boot

        15.2K
        13.1K
        874
        Create Spring-powered, production-grade applications and services with absolute minimum fuss
        15.2K
        13.1K
        + 1
        874
        PROS OF SPRING BOOT
        • 131
          Powerful and handy
        • 122
          Easy setup
        • 115
          Java
        • 84
          Spring
        • 81
          Fast
        • 40
          Extensible
        • 33
          Lots of "off the shelf" functionalities
        • 28
          Cloud Solid
        • 22
          Caches well
        • 20
          Many receipes around for obscure features
        • 19
          Modular
        • 19
          Productive
        • 18
          Integrations with most other Java frameworks
        • 17
          Spring ecosystem is great
        • 17
          Fast Performance With Microservices
        • 15
          Community
        • 14
          Auto-configuration
        • 12
          Easy setup, Community Support, Solid for ERP apps
        • 12
          One-stop shop
        • 11
          Cross-platform
        • 11
          Easy to parallelize
        • 10
          Easy setup, good for build erp systems, well documented
        • 10
          Powerful 3rd party libraries and frameworks
        • 9
          Easy setup, Git Integration
        • 2
          Kotlin
        • 2
          It's so easier to start a project on spring
        CONS OF SPRING BOOT
        • 18
          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 · 1.8M 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
        AngularJS logo

        AngularJS

        42K
        29.7K
        5.3K
        Superheroic JavaScript MVW Framework
        42K
        29.7K
        + 1
        5.3K
        PROS OF ANGULARJS
        • 886
          Quick to develop
        • 587
          Great mvc
        • 571
          Powerful
        • 522
          Restful
        • 504
          Backed by google
        • 349
          Two-way data binding
        • 344
          Javascript
        • 328
          Open source
        • 306
          Dependency injection
        • 198
          Readable
        • 76
          Fast
        • 65
          Directives
        • 64
          Great community
        • 57
          Free
        • 39
          Extend html vocabulary
        • 30
          Components
        • 26
          Easy to test
        • 25
          Easy to learn
        • 24
          Easy to templates
        • 24
          Great documentation
        • 22
          Easy to start
        • 18
          Awesome
        • 18
          Light weight
        • 15
          Angular 2.0
        • 15
          Javascript mvw framework
        • 14
          Great extensions
        • 14
          Efficient
        • 11
          Easy to prototype with
        • 9
          High performance
        • 9
          Coffeescript
        • 8
          Mvc
        • 8
          Two-way binding
        • 8
          Lots of community modules
        • 7
          Easy to e2e
        • 7
          Clean and keeps code readable
        • 6
          One of the best frameworks
        • 6
          Easy for small applications
        • 5
          Works great with jquery
        • 5
          Fast development
        • 3
          Hierarchical Data Structure
        • 3
          The two-way Data Binding is awesome
        • 3
          Community
        • 3
          Typescript
        • 3
          Declarative programming
        • 3
          I do not touch DOM
        • 3
          Be a developer, not a plumber.
        • 3
          Dart
        • 2
          Fkin awesome
        • 2
          Scopes
        • 2
          The powerful of binding, routing and controlling routes
        • 2
          Opinionated in the right areas
        • 2
          Supports api , easy development
        • 2
          Common Place
        • 2
          Amazing community support
        • 2
          Great
        • 2
          Very very useful and fast framework for development
        • 2
          Readable code
        • 2
          Programming fun again
        • 2
          Linear learning curve
        • 1
          Bot Ionescu
        • 1
          Acoperișul 0757604335
        • 1
          Js
        • 1
          Google.com
        • 1
          Angular js
        • 1
          Httpș//Acoperișul 0757604335
        • 1
          Shvzjn
        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 · | 24 upvotes · 1.7M 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 · | 19 upvotes · 580.1K 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
        JBoss logo

        JBoss

        177
        156
        0
        An open source Java EE-based application server
        177
        156
        + 1
        0
        PROS OF JBOSS
          Be the first to leave a pro
          CONS OF JBOSS
            Be the first to leave a con

            related JBoss posts

            Node.js logo

            Node.js

            109.3K
            89K
            8.3K
            A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
            109.3K
            89K
            + 1
            8.3K
            PROS OF NODE.JS
            • 1.4K
              Npm
            • 1.3K
              Javascript
            • 1.1K
              Great libraries
            • 1K
              High-performance
            • 791
              Open source
            • 480
              Great for apis
            • 471
              Asynchronous
            • 417
              Great community
            • 387
              Great for realtime apps
            • 292
              Great for command line utilities
            • 78
              Node Modules
            • 76
              Websockets
            • 65
              Uber Simple
            • 53
              Great modularity
            • 53
              Allows us to reuse code in the frontend
            • 38
              Easy to start
            • 33
              Great for Data Streaming
            • 29
              Realtime
            • 25
              Awesome
            • 23
              Non blocking IO
            • 16
              Can be used as a proxy
            • 15
              High performance, open source, scalable
            • 14
              Non-blocking and modular
            • 13
              Easy and Fun
            • 12
              Same lang as AngularJS
            • 11
              Easy and powerful
            • 10
              Future of BackEnd
            • 9
              Fast
            • 8
              Scalability
            • 8
              Cross platform
            • 8
              Fullstack
            • 7
              Mean Stack
            • 7
              Simple
            • 5
              Easy concurrency
            • 5
              Great for webapps
            • 5
              React
            • 4
              Friendly
            • 4
              Easy to use and fast and goes well with JSONdb's
            • 4
              Typescript
            • 4
              Fast, simple code and async
            • 3
              Its amazingly fast and scalable
            • 3
              Scalable
            • 3
              Great speed
            • 3
              Fast development
            • 3
              Isomorphic coolness
            • 3
              Control everything
            • 2
              It's fast
            • 2
              Not Python
            • 2
              Blazing fast
            • 2
              One language, end-to-end
            • 2
              TypeScript Support
            • 2
              Easy to learn
            • 2
              Javascript2
            • 2
              Easy to use
            • 2
              Less boilerplate code
            • 2
              Sooper easy for the Backend connectivity
            • 2
              Great community
            • 2
              Scales, fast, simple, great community, npm, express
            • 2
              Performant and fast prototyping
            • 1
              Easy
            • 1
              Lovely
            • 0
              Event Driven
            CONS OF NODE.JS
            • 46
              Bound to a single CPU
            • 40
              New framework every day
            • 34
              Lots of terrible examples on the internet
            • 28
              Asynchronous programming is the worst
            • 22
              Callback
            • 16
              Javascript
            • 11
              Dependency based on GitHub
            • 10
              Dependency hell
            • 10
              Low computational power
            • 7
              Can block whole server easily
            • 6
              Very very Slow
            • 6
              Callback functions may not fire on expected sequence
            • 3
              Unneeded over complication
            • 3
              Unstable
            • 3
              Breaking updates
            • 1
              No standard approach

            related Node.js posts

            Nick Rockwell
            SVP, Engineering at Fastly · | 42 upvotes · 1.6M views

            When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

            So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

            React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

            Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

            See more
            Conor Myhrvold
            Tech Brand Mgr, Office of CTO at Uber · | 38 upvotes · 3.7M views

            How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

            Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

            Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

            https://eng.uber.com/distributed-tracing/

            (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

            Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

            See more
            Django logo

            Django

            23.9K
            20.7K
            3.6K
            The Web framework for perfectionists with deadlines
            23.9K
            20.7K
            + 1
            3.6K
            PROS OF DJANGO
            • 619
              Rapid development
            • 459
              Open source
            • 394
              Great community
            • 344
              Easy to learn
            • 256
              Mvc
            • 208
              Beautiful code
            • 207
              Elegant
            • 187
              Free
            • 186
              Great packages
            • 173
              Great libraries
            • 63
              Restful
            • 60
              Powerful
            • 59
              Comes with auth and crud admin panel
            • 55
              Great documentation
            • 52
              Great for web
            • 41
              Python
            • 35
              Great orm
            • 31
              Great for api
            • 24
              All included
            • 20
              Web Apps
            • 19
              Fast
            • 16
              Used by top startups
            • 14
              Clean
            • 13
              Sexy
            • 12
              Easy setup
            • 10
              Convention over configuration
            • 7
              ORM
            • 7
              Allows for very rapid development with great libraries
            • 7
              The Django community
            • 5
              Its elegant and practical
            • 5
              Great MVC and templating engine
            • 4
              Full stack
            • 4
              Mvt
            • 4
              Easy Structure , useful inbuilt library
            • 4
              Fast prototyping
            • 4
              Easy to develop end to end AI Models
            • 3
              Easy
            • 3
              Easy to use
            • 3
              King of backend world
            • 3
              Cross-Platform
            • 3
              Batteries included
            • 3
              Have not found anything that it can't do
            • 2
              Scaffold
            • 2
              Zero code burden to change databases
            • 2
              Full-Text Search
            • 2
              Map
            • 2
              Modular
            • 2
              Very quick to get something up and running
            • 2
              Many libraries
            • 2
              Python community
            • 2
              Great peformance
            • 2
              Just the right level of abstraction
            • 1
              Easy to change database manager
            CONS OF DJANGO
            • 24
              Underpowered templating
            • 19
              Underpowered ORM
            • 18
              Autoreload restarts whole server
            • 15
              URL dispatcher ignores HTTP method
            • 10
              Internal subcomponents coupling
            • 7
              Not nodejs
            • 7
              Admin
            • 6
              Configuration hell
            • 3
              Not as clean and nice documentation like Laravel
            • 3
              Bloated admin panel included
            • 3
              Python
            • 2
              Overwhelming folder structure
            • 2
              Not typed
            • 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