Перейти к основному содержимому

State of JavaScript 2025

Бэкенд-фреймворки

JavaScript на сервере.

Back-end Frameworks Ratios Over Time

After three years of absence from the survey, it was high time we checked back on back-end frameworks. And no surprise here, Express is still the leader in terms of usage, even if Next is progressing at a nice clip.

But things are more interesting when switching to the Satisfactiont tab, where the top three projects (Hono, Nitro, and ElysiaJS) are all new entrants, making this once of the most exciting categories to watch in years to come.

Express
NestJS
Fastify
Strapi
Hono
Koa
ElysiaJS
Adonis
Hapi
Directus
tRPC
Nitro

Mode:

View:

Использование:

Proportion of respondents having used an item
0%
20%
40%
60%
80%
100%
2017
2018
2019
2020
2021
2022
2023
2024
2025
0%
20%
40%
60%
80%
100%

Other Back-end Frameworks

oRPC offers typesafe APIs, which is a big selling point compared to traditional back-end solutions created before the TypeScript sea change.

0%
20%
40%
60%
80%
100%
1
34
2
24
3
payload
20
4
17
5
effect
14
6
13
7
10
8
Other Answers
122
0%
20%
40%
60%
80%
100%
% ответивших на вопрос
235
2%
10
We asked members of the JavaScript community to share their “pick of the year”

My 2025 Pick: The Atproto Dev Community

I think the atproto dev community deserves a spotlight - one of the official SDKs is TypeScript! Also shout-out to Jason Lengstorf and everyone else involved in this.
We asked members of the JavaScript community to share their “pick of the year”

Jenn Schiffer

Reknowned candle-maker and karaoke professional

Number of Items

Respondents tend to use relatively few back-end frameworks, which might be why Express remains so dominant: once you've picked a back-end, you're unlikely to go out of your way to try out new options.

0%
5%
10%
16%
21%
26%
01
0
2,868
02
1
3,387
03
2
2,772
04
3
1,842
05
4
1,030
06
5
566
07
6
276
08
7
140
09
8
69
10
9
37
11
10
8
12
11
2
13
12
5
0%
5%
10%
16%
21%
26%
% респондентов опроса
1.9

Back-end Frameworks Pain Points

While *Express is still widely used 15 years after its initial release, some are starting to wish the back-end ecosystem would move on to more modern alternatives.

This is especially true when it comes to providing typesafe, TypeScript-compatible APIs, which is something that venerable framework was never meant to do.

0%
20%
40%
60%
80%
100%
01
02
Static typing
03
Browser support
04
Performance
05
06
Excessive complexity
07
Lack of documentation
08
Choice overload
09
10
Frontend testing
0%
20%
40%
60%
80%
100%
% ответивших на вопрос
1,059
8%
20
10

Рекомендуемые ресурсы

API Design in Node.js, v5
Scott Moss
Netflix

API Design in Node.js, v5

Build scalable APIs for any application with Node.js and Express. Learn RESTful API design best practices as you design routes, run Postgres migrations, and secure your API with JWT-based authentication.
Backend System Design
Jem Young
Netflix

Backend System Design

Grab your favorite diagramming tool and develop the system-thinking skills to solve complex backend design challenges related to scaling, data storage, reliability, and performance.
Спасибо нашим партнёрам за поддержку! Подробнее.