StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Frameworks
  4. Frameworks
  5. NestJS vs React on Rails

NestJS vs React on Rails

OverviewDecisionsComparisonAlternatives

Overview

NestJS
NestJS
Stacks2.7K
Followers3.0K
Votes326
GitHub Stars73.3K
Forks8.1K
React on Rails
React on Rails
Stacks25
Followers54
Votes0
GitHub Stars5.2K
Forks639

NestJS vs React on Rails: What are the differences?

Key Differences between NestJS and React on Rails

Introduction

Here are the key differences between NestJS and React on Rails:

  1. Architecture: NestJS is a backend framework that follows a modular and MVC (Model-View-Controller) oriented architecture, while React on Rails combines the React frontend framework with the Ruby on Rails backend framework.

  2. Language: NestJS is written in TypeScript, which is a statically-typed superset of JavaScript, while React on Rails is primarily written in Ruby.

  3. Backend vs. Full-stack: NestJS is primarily focused on providing a robust backend solution, providing features like routing, controllers, services, and dependency injection. React on Rails, on the other hand, is a full-stack framework that combines frontend and backend development, integrating Ruby on Rails with React.

  4. Frontend Framework: NestJS does not come with a specific frontend framework or library but can be used with any frontend technology, including React. React on Rails, however, is specifically designed to work with React as the frontend framework.

  5. Server-side Rendering: NestJS does not have built-in server-side rendering capabilities. It mainly focuses on building APIs and backend logic. In contrast, React on Rails has built-in server-side rendering support, allowing for faster initial page load and better SEO (Search Engine Optimization).

  6. Community Support: React on Rails has a larger and more established community compared to NestJS. This means that there are more resources, tutorials, and plugins available for React on Rails, making it easier to find solutions and get support when working on projects.

In summary, NestJS is a backend framework that follows a modular and MVC architecture, written in TypeScript, and can be used with any frontend technology. React on Rails is a full-stack framework that combines Ruby on Rails with React, provides server-side rendering, and has a larger community support.

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)
or
Manual

Advice on NestJS, React on Rails

juan9222
juan9222

Jul 25, 2020

Needs advice

Hi there, I'm deciding the technology to use in my project.

I need to build software that has:

  • Login
  • Register
  • Main View (access to a user account, News, General Info, Business hours, software, and parts section).
  • Account Preferences.
  • Web Shop for Parts (Support, Download Sections, Ticket System).

The most critical functionality is a WebSocket that connects between a car that sends real-time data through serial communication, and a server performs diagnosis on the car and sends the results back to the user.

616k views616k
Comments
Louai
Louai

Full Stack Web Developer

May 15, 2020

Needs adviceonNode.jsNode.jsTypeScriptTypeScriptExpressJSExpressJS

I'm planning with a small team to create an application which is a platform for restaurants. I'm on the backend almost alone currently. I'm going to use Node.js for that, and I'm very fond of TypeScript, and I worked before mostly with ExpressJS. The team may get bigger as the application becomes bigger and more successful, so I have the Scalability concern in mind now, and I was considering these options:

  1. Use Node+Express+Typescript
  2. Use Node+NestJs (which utilizes Typescript by default)

Option 2 is enticing to me because recently I came to love NestJS and it provides more scalability for the project and uses Typescript in the best way and uses Express under the hood. Also I come from an Angular 2 background, which I think is the best frontend framework (my opinion, and I know React quite well), which makes Nest feel familiar to me because of the similarity between Nest and Angular. Option 1 on the other hand uses Express which is a minimalist framework, very popular one, but it doesn't provide the same scalability and brings decision fatigue about what to combine with it and may not utilize Typescript in the best way. Yet, on the other hand, it is flexible and it may be easier to manipulate things in different ways with it. Another very important thing is that it would be easier in my view to hire Node developers with skills in Express than NestJs. The majority of Node developers are much more familiar with JavaScript and Express.

What is your advice and why? I would love to hear especially from developers who worked on both Express and Nest

549k views549k
Comments
Slimane
Slimane

Jul 9, 2020

Needs adviceonSpring BootSpring BootNestJSNestJSNode.jsNode.js

I am currently planning to build a project from scratch. I will be using Angular as front-end framework, but for the back-end I am not sure which framework to use between Spring Boot and NestJS. I have worked with Spring Boot before, but my new project contains a lot of I/O operations, in fact it will show a daily report. I thought about the new Spring Web Reactive Framework but given the idea that Node.js is the most popular on handling non blocking I/O I am planning to start learning NestJS since it is based on Angular philosophy and TypeScript which I am familiar with. Looking forward to hear from you dear Community.

917k views917k
Comments

Detailed Comparison

NestJS
NestJS
React on Rails
React on Rails

Nest is a framework for building efficient, scalable Node.js server-side applications. It uses progressive JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming). Under the hood, Nest makes use of Express, but also, provides compatibility with a wide range of other libraries, like e.g. Fastify, allowing for easy use of the myriad third-party plugins which are available.

Project Objective: To provide an opinionated and optimal framework for integrating Ruby on Rails with React via the Webpacker gem. React on Rails integrates Facebook's React front-end framework with Rails. React v0.14.x and greater is supported, with server rendering. Redux and React-Router are supported as well, also with server rendering, using execJS.

Extensible - Gives you true flexibility by allowing use of any other libraries thanks to modular architecture.; Versatile - An adaptable ecosystem that is a fully-fledged backbone for all kinds of server-side applications.; Progressive - Takes advantage of latest JavaScript features, bringing design patterns and mature solutions to node.js world.
server-side rendering; turbolinks compatibility; redux support; react-router support; webpacker support; internationalization
Statistics
GitHub Stars
73.3K
GitHub Stars
5.2K
GitHub Forks
8.1K
GitHub Forks
639
Stacks
2.7K
Stacks
25
Followers
3.0K
Followers
54
Votes
326
Votes
0
Pros & Cons
Pros
  • 54
    Powerful but super friendly to work with
  • 42
    Fast development
  • 40
    Easy to understand documentation
  • 36
    Angular style syntax for the backend
  • 32
    NodeJS ecosystem
Cons
  • 10
    User base is small. Less help on Stackoverflow
  • 10
    Difficult to debug
  • 5
    Angular-like architecture
  • 3
    Javascript
  • 3
    Updates with breaking changes
No community feedback yet

What are some alternatives to NestJS, React on Rails?

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.

Rails

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.

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.

.NET

.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

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.

Symfony

Symfony

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

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.

Android SDK

Android SDK

Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase