React vs Spring MVC

Overview

React

Stacks182.6K

Followers147.0K

Votes4.1K

GitHub Stars240.3K

Forks49.7K

Spring MVC

Stacks479

Followers519

Votes0

GitHub Stars59.1K

Forks38.8K

React vs Spring MVC: What are the differences?

Key Differences between React and Spring MVC

React is a popular JavaScript library used for building user interfaces, while Spring MVC is a Java framework used for building web applications. Here are the key differences between React and Spring MVC:

Architecture: React follows a component-based architecture, where the user interface is divided into reusable components. On the other hand, Spring MVC follows a Model-View-Controller (MVC) architecture that separates the application into models, views, and controllers.
Language: React is primarily based on JavaScript, while Spring MVC is based on Java. This means that developers with JavaScript expertise would find it easier to work with React, whereas developers with Java expertise would find it easier to work with Spring MVC.
Server-side Rendering: React is primarily a client-side rendering library, meaning that the initial rendering of the application happens on the client-side. In contrast, Spring MVC supports server-side rendering, where the rendering of the application happens on the server before being sent to the client.
State Management: React has a built-in state management system, where the state of the components can be managed efficiently. Spring MVC, on the other hand, relies on the usage of HTTP session or other server-side mechanisms for managing the state of the application.
Development Speed: React allows for rapid development as it provides a set of ready-to-use components and a declarative syntax, which makes the development process faster. In comparison, Spring MVC requires more configuration and setup, which can slow down the development process.
Reusability: React promotes the reusability of components, which allows for faster development and easier maintenance of the codebase. Spring MVC also supports reusability through the use of Java classes and design patterns, but it may require more effort to achieve the same level of reusability as React.

In summary, React and Spring MVC differ in terms of architecture, language, rendering approach, state management, development speed, and reusability. React is more focused on client-side rendering, while Spring MVC supports server-side rendering. React has a built-in state management system, while Spring MVC relies on server-side mechanisms. React allows for faster development due to its ready-to-use components and declarative syntax, whereas Spring MVC requires more configuration and setup. Both frameworks support reusability, but React promotes it more through its component-based architecture.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on React, Spring MVC

Cyrus

Aug 15, 2019

Needs adviceon

Vue.js

React

I find using Vue.js to be easier (more concise / less boilerplate) and more intuitive than writing React. However, there are a lot more readily available React components that I can just plug into my projects. I'm debating whether to use Vue.js or React for an upcoming project that I'm going to use to help teach a friend how to build an interactive frontend. Which would you recommend I use?

884k views884k

Comments

Cyrus

Aug 15, 2019

Needs advice

Simple datepickers are cumbersome. For such a simple data input, I feel like it takes far too much effort. Ideally, the native input[type="date"] would just work like it does on FF and Chrome, but Safari and Edge don't handle it properly. So I'm left either having a diverging experience based on the browser or I need to choose a library to implement a datepicker since users aren't good at inputing formatted strings.

For React alone there are tons of examples to use https://reactjsexample.com/tag/date/. And then of course there's the bootstrap datepicker (https://bootstrap-datepicker.readthedocs.io/en/latest/), jQueryUI calendar picker, https://github.com/flatpickr/flatpickr, and many more.

How do you recommend going about handling date and time inputs? And then there's always moment.js, but I've observed some users getting stuck when presented with a blank text field. I'm curious to hear what's worked well for people...

401k views401k

Comments

Malek

Web developer at Quicktext

Mar 28, 2020

Decided

The project is a web gadget previously made using vanilla script and JQuery, It is a part of the "Quicktext" platform and offers an in-app live & customizable messaging widget. We made that remake with React eco-system and Typescript and we're so far happy with results. We gained tons of TS features, React scaling & re-usabilities capabilities and much more!

What do you think?

244k views244k

Comments

Detailed Comparison

React	Spring MVC
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.	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.
Declarative; Component-based; Learn once, write anywhere	Clear separation of roles; Customizable binding and validation; Adaptability; Flexibility
Statistics
GitHub Stars 240.3K	GitHub Stars 59.1K
GitHub Forks 49.7K	GitHub Forks 38.8K
Stacks 182.6K	Stacks 479
Followers 147.0K	Followers 519
Votes 4.1K	Votes 0
Pros & Cons
Pros 837 Components 674 Virtual dom 579 Performance 509 Simplicity 442 Composable Cons 41 Requires discipline to keep architecture organized 30 No predefined way to structure your app 29 Need to be familiar with lots of third party packages 13 JSX 10 Not enterprise friendly	No community feedback yet
Integrations
No integrations available	AngularJS Bootstrap Spring Boot Hibernate

What are some alternatives to React, Spring MVC?

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.

jQuery

jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML.

Rails

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

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.

Django

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

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.

.NET

.NET is a general purpose development platform. With .NET, you can use multiple languages, editors, and libraries to build native applications for web, mobile, desktop, gaming, and IoT for Windows, macOS, Linux, Android, and more.

ASP.NET Core

A free and open-source web framework, and higher performance than ASP.NET, developed by Microsoft and the community. It is a modular framework that runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core.

Vue.js

It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API.

Symfony

It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP..

Related Comparisons

React vs Spring MVC: What are the differences?

Key Differences between React and Spring MVC

Architecture: React follows a component-based architecture, where the user interface is divided into reusable components. On the other hand, Spring MVC follows a Model-View-Controller (MVC) architecture that separates the application into models, views, and controllers.
Language: React is primarily based on JavaScript, while Spring MVC is based on Java. This means that developers with JavaScript expertise would find it easier to work with React, whereas developers with Java expertise would find it easier to work with Spring MVC.
Server-side Rendering: React is primarily a client-side rendering library, meaning that the initial rendering of the application happens on the client-side. In contrast, Spring MVC supports server-side rendering, where the rendering of the application happens on the server before being sent to the client.
State Management: React has a built-in state management system, where the state of the components can be managed efficiently. Spring MVC, on the other hand, relies on the usage of HTTP session or other server-side mechanisms for managing the state of the application.
Development Speed: React allows for rapid development as it provides a set of ready-to-use components and a declarative syntax, which makes the development process faster. In comparison, Spring MVC requires more configuration and setup, which can slow down the development process.
Reusability: React promotes the reusability of components, which allows for faster development and easier maintenance of the codebase. Spring MVC also supports reusability through the use of Java classes and design patterns, but it may require more effort to achieve the same level of reusability as React.

React vs Spring MVC

Overview

React vs Spring MVC: What are the differences?