ServiceStack vs NestJS

Overview

ServiceStack

Stacks191

Followers49

Votes0

NestJS

Stacks2.7K

Followers3.0K

Votes326

GitHub Stars73.3K

Forks8.1K

NestJS vs ServiceStack: What are the differences?

NestJS: A progressive Node.js framework for building efficient and scalable server-side applications by @kammysliwiec. 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.; ServiceStack: *A configuration free, code-first, light-weight framework *. It is a configuration free, code-first, light-weight framework built on top of ASP.NET for building services and web applications. As the name suggests, it is a stack of services. It provides with just everything that one needs for building end-to-end web services.

NestJS and ServiceStack can be primarily classified as "Frameworks (Full Stack)" tools.

NestJS is an open source tool with 18.3K GitHub stars and 1.31K GitHub forks. Here's a link to NestJS's open source repository on GitHub.

🔥 Trending in Frameworks on StackShare

Node.js Frameworks

A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications

Try it View Docs Alternatives

Try

566

165k

Advice on ServiceStack, NestJS

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

Full Stack Web Developer

May 15, 2020

Needs adviceon

Node.js

TypeScript

ExpressJS

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:

Use Node+Express+Typescript
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

Jul 9, 2020

Needs adviceon

Spring Boot

NestJS

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

ServiceStack	NestJS
It is a configuration free, code-first, light-weight framework built on top of ASP.NET for building services and web applications. As the name suggests, it is a stack of services. It provides with just everything that one needs for building end-to-end web services.	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.
-	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.
Statistics
GitHub Stars -	GitHub Stars 73.3K
GitHub Forks -	GitHub Forks 8.1K
Stacks 191	Stacks 2.7K
Followers 49	Followers 3.0K
Votes 0	Votes 326
Pros & Cons
No community feedback yet	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
Integrations
AngularJS MongoDB	No integrations available

What are some alternatives to ServiceStack, NestJS?

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

Symfony

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

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