Alternatives to Spring Framework logo

Alternatives to Spring Framework

Spring MVC, Spring Boot, Play, Java EE, and Django are the most popular alternatives and competitors to Spring Framework.
747
574
+ 1
0

What is Spring Framework and what are its top alternatives?

It provides a comprehensive programming and configuration model for modern Java-based enterprise applications - on any kind of deployment platform. The framework's core features can be used by any Java application, but there are extensions for building web applications on top of the Java EE platform.
Spring Framework is a tool in the Frameworks (Full Stack) category of a tech stack.
Spring Framework is an open source tool with 45K GitHub stars and 31.7K GitHub forks. Here’s a link to Spring Framework's open source repository on GitHub

Top Alternatives to Spring Framework

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

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

  • Java EE

    Java EE

    It is developed using the Java Community Process, with contributions from industry experts, commercial and open source organizations, Java User Groups, and countless individuals. It offers a rich enterprise software platform and with over 20 compliant implementations to choose from. ...

  • Django

    Django

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

  • Laravel

    Laravel

    It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching. ...

  • Hibernate

    Hibernate

    Hibernate is a suite of open source projects around domain models. The flagship project is Hibernate ORM, the Object Relational Mapper. ...

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

Spring Framework alternatives & related posts

Spring MVC logo

Spring MVC

421
416
0
A Java framework which is used to build web applications
421
416
+ 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 · 129.2K 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 Boot logo

      Spring Boot

      16.9K
      14.9K
      914
      Create Spring-powered, production-grade applications and services with absolute minimum fuss
      16.9K
      14.9K
      + 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
      Play logo

      Play

      689
      513
      495
      The High Velocity Web Framework For Java and Scala
      689
      513
      + 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
      Java EE logo

      Java EE

      441
      364
      2
      The standard in community-driven enterprise software
      441
      364
      + 1
      2
      PROS OF JAVA EE
      • 1
        Inherits all java advantages
      • 1
        High level of security
      CONS OF JAVA EE
      • 2
        PAID

      related Java EE posts

      Shared insights
      on
      JavaScriptJavaScriptJava EEJava EE

      Hi, I'm looking to learn Java EE and JavaScript.... but confused about exactly the difference between J2EE and JavaScript.....are both interconnected or different??? And if I want to learn both, should I learn JavaScript first and then touch J2EE or learn J2EE first and then JavaScript??.... please suggest

      See more
      Django logo

      Django

      26.4K
      23.3K
      3.8K
      The Web framework for perfectionists with deadlines
      26.4K
      23.3K
      + 1
      3.8K
      PROS OF DJANGO
      • 631
        Rapid development
      • 467
        Open source
      • 400
        Great community
      • 352
        Easy to learn
      • 263
        Mvc
      • 214
        Beautiful code
      • 210
        Elegant
      • 192
        Free
      • 190
        Great packages
      • 178
        Great libraries
      • 67
        Restful
      • 65
        Comes with auth and crud admin panel
      • 65
        Powerful
      • 59
        Great documentation
      • 57
        Great for web
      • 43
        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
      • 9
        ORM
      • 9
        Allows for very rapid development with great libraries
      • 8
        The Django community
      • 6
        Its elegant and practical
      • 6
        Great MVC and templating engine
      • 5
        King of backend world
      • 5
        Easy to develop end to end AI Models
      • 5
        Have not found anything that it can't do
      • 5
        Mvt
      • 5
        Fast prototyping
      • 5
        Full stack
      • 5
        Easy Structure , useful inbuilt library
      • 4
        Cross-Platform
      • 4
        Easy to use
      • 4
        Batteries included
      • 4
        Easy
      • 3
        Map
      • 3
        Full-Text Search
      • 3
        Zero code burden to change databases
      • 3
        Modular
      • 3
        Scaffold
      • 3
        Just the right level of abstraction
      • 3
        Very quick to get something up and running
      • 3
        Many libraries
      • 3
        Python community
      • 3
        Great peformance
      • 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
      Laravel logo

      Laravel

      20.2K
      16.1K
      3.5K
      A PHP Framework For Web Artisans
      20.2K
      16.1K
      + 1
      3.5K
      PROS OF LARAVEL
      • 513
        Clean architecture
      • 374
        Growing community
      • 348
        Composer friendly
      • 321
        Open source
      • 303
        The only framework to consider for php
      • 201
        Mvc
      • 194
        Quickly develop
      • 159
        Dependency injection
      • 147
        Application architecture
      • 134
        Embraces good community packages
      • 62
        Write less, do more
      • 55
        Restful routing
      • 51
        Orm (eloquent)
      • 47
        Artisan scaffolding and migrations
      • 46
        Database migrations & seeds
      • 36
        Awesome
      • 34
        Great documentation
      • 26
        Awsome, Powerfull, Fast and Rapid
      • 25
        Promotes elegant coding
      • 25
        Build Apps faster, easier and better
      • 22
        JSON friendly
      • 22
        Easy to learn, scalability
      • 21
        Eloquent ORM
      • 21
        Modern PHP
      • 21
        Most easy for me
      • 20
        Test-Driven
      • 19
        Blade Template
      • 18
        Beautiful
      • 13
        Security
      • 12
        Based on SOLID
      • 11
        Simple
      • 11
        Clean Documentation
      • 11
        Cool
      • 10
        Easy to attach Middleware
      • 10
        Convention over Configuration
      • 9
        Easy Request Validatin
      • 8
        Easy to use
      • 8
        Its just wow
      • 8
        Simpler
      • 8
        Get going quickly straight out of the box. BYOKDM
      • 8
        Laravel + Cassandra = Killer Framework
      • 8
        Fast
      • 7
        Less dependencies
      • 7
        Friendly API
      • 7
        Super easy and powerful
      • 7
        Simplistic , easy and faster
      • 6
        Great customer support
      • 6
        Its beautiful to code in
      • 5
        The only "cons" is wrong! No static method just Facades
      • 5
        Fast and Clarify framework
      • 5
        Active Record
      • 5
        Php7
      • 5
        Speed
      • 5
        Easy
      • 4
        Composer
      • 4
        Laravel Mix
      • 4
        Minimum system requirements
      • 4
        Easy views handling and great ORM
      • 4
        Eloquent
      • 4
        Laragon
      • 3
        Laravel Nova
      • 3
        Laravel casher
      • 3
        Laravel Passport
      • 3
        Ease of use
      • 3
        Cashier with Braintree and Stripe
      • 3
        Laravel Forge and Envoy
      • 3
        Laravel Horizon and Telescope
      • 3
        Laravel Spark
      • 3
        Intuitive usage
      • 2
        Heart touch
      • 2
        Like heart beat
      • 2
        Rapid development
      • 2
        Laravel love live long
      • 2
        Touch heart artisan
      • 2
        Scout
      CONS OF LARAVEL
      • 42
        PHP
      • 28
        Too many dependency
      • 20
        Slower than the other two
      • 16
        A lot of static method calls for convenience
      • 13
        Too many include
      • 10
        Heavy
      • 7
        Bloated
      • 6
        Laravel
      • 5
        Confusing
      • 4
        Does not work well for file uploads in Shared Hosting
      • 4
        Too underrated
      • 2
        Not fast with MongoDB
      • 1
        Difficult to learn
      • 1
        Not using SOLID principles

      related Laravel posts

      I need to build a web application plus android and IOS apps for an enterprise, like an e-commerce portal. It will have intensive use of MySQL to display thousands (40-50k) of live product information in an interactive table (searchable, filterable), live delivery tracking. It has to be secure, as it will handle information on customers, sales, inventory. Here is the technology stack: Backend: Laravel 7 Frondend: Vue.js, React or AngularJS?

      Need help deciding technology stack. Thanks.

      See more
      Antonio Sanchez

      Back at the start of 2017, we decided to create a web-based tool for the SEO OnPage analysis of our clients' websites. We had over 2.000 websites to analyze, so we had to perform thousands of requests to get every single page from those websites, process the information and save the big amounts of data somewhere.

      Very soon we realized that the initial chosen script language and database, PHP, Laravel and MySQL, was not going to be able to cope efficiently with such a task.

      By that time, we were doing some experiments for other projects with a language we had recently get to know, Go , so we decided to get a try and code the crawler using it. It was fantastic, we could process much more data with way less CPU power and in less time. By using the concurrency abilites that the language has to offers, we could also do more Http requests in less time.

      Unfortunately, I have no comparison numbers to show about the performance differences between Go and PHP since the difference was so clear from the beginning and that we didn't feel the need to do further comparison tests nor document it. We just switched fully to Go.

      There was still a problem: despite the big amount of Data we were generating, MySQL was performing very well, but as we were adding more and more features to the software and with those features more and more different type of data to save, it was a nightmare for the database architects to structure everything correctly on the database, so it was clear what we had to do next: switch to a NoSQL database. So we switched to MongoDB, and it was also fantastic: we were expending almost zero time in thinking how to structure the Database and the performance also seemed to be better, but again, I have no comparison numbers to show due to the lack of time.

      We also decided to switch the website from PHP and Laravel to JavaScript and Node.js and ExpressJS since working with the JSON Data that we were saving now in the Database would be easier.

      As of now, we don't only use the tool intern but we also opened it for everyone to use for free: https://tool-seo.com

      See more
      Hibernate logo

      Hibernate

      1.2K
      937
      24
      Idiomatic persistence for Java and relational databases.
      1.2K
      937
      + 1
      24
      PROS OF HIBERNATE
      • 16
        Easy ORM
      • 7
        Easy transaction definition
      • 1
        Is integrated with spring jpa
      CONS OF HIBERNATE
      • 3
        Can't control proxy associations when entity graph used

      related Hibernate posts

      Node.js logo

      Node.js

      122.7K
      102.9K
      8.4K
      A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
      122.7K
      102.9K
      + 1
      8.4K
      PROS OF NODE.JS
      • 1.4K
        Npm
      • 1.3K
        Javascript
      • 1.1K
        Great libraries
      • 1K
        High-performance
      • 795
        Open source
      • 484
        Great for apis
      • 474
        Asynchronous
      • 420
        Great community
      • 390
        Great for realtime apps
      • 295
        Great for command line utilities
      • 81
        Node Modules
      • 80
        Websockets
      • 67
        Uber Simple
      • 57
        Great modularity
      • 56
        Allows us to reuse code in the frontend
      • 40
        Easy to start
      • 35
        Great for Data Streaming
      • 31
        Realtime
      • 26
        Awesome
      • 24
        Non blocking IO
      • 17
        Can be used as a proxy
      • 16
        High performance, open source, scalable
      • 15
        Non-blocking and modular
      • 14
        Easy and Fun
      • 12
        Easy and powerful
      • 12
        Same lang as AngularJS
      • 11
        Future of BackEnd
      • 10
        Fast
      • 9
        Fullstack
      • 9
        Scalability
      • 9
        Cross platform
      • 8
        Simple
      • 7
        Mean Stack
      • 6
        Great for webapps
      • 6
        Easy concurrency
      • 5
        Friendly
      • 5
        Fast, simple code and async
      • 5
        React
      • 4
        Great speed
      • 4
        Fast development
      • 4
        Its amazingly fast and scalable
      • 4
        Control everything
      • 4
        Easy to use and fast and goes well with JSONdb's
      • 4
        Typescript
      • 4
        Scalable
      • 3
        It's fast
      • 3
        Easy to use
      • 3
        Isomorphic coolness
      • 2
        Sooper easy for the Backend connectivity
      • 2
        Easy to learn
      • 2
        TypeScript Support
      • 2
        Scales, fast, simple, great community, npm, express
      • 2
        One language, end-to-end
      • 2
        Javascript2
      • 2
        Not Python
      • 2
        Performant and fast prototyping
      • 2
        Blazing fast
      • 2
        Great community
      • 2
        Less boilerplate code
      • 2
        Easy
      • 1
        Lovely
      • 1
        Event Driven
      CONS OF NODE.JS
      • 46
        Bound to a single CPU
      • 42
        New framework every day
      • 35
        Lots of terrible examples on the internet
      • 29
        Asynchronous programming is the worst
      • 23
        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 · | 44 upvotes · 1.7M 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 · | 39 upvotes · 4.2M 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