H
H
HoHsi2016-03-12 19:30:16
Node.js
HoHsi, 2016-03-12 19:30:16

Which web framework for Node.js should you choose?

Good afternoon!
I was pretty fed up with Express, due to the fact that there you need to do almost everything by hand (this is undoubtedly power, but not in the current case).
Now I'm developing a service that handles rather long tasks using AMQP, and I need to attach a Web face to all this.
I know and love Express with all my heart (especially in conjunction with Exa), but now it seems to me redundant and long in development.
Appeared in need, albeit less flexible, but fast in terms of development framework.
The criteria are:
* ES6/ES7 syntax, with async/await (well, or at least CO, which are quietly replaced by ES7 async/await).
* Ability to select a database. I know and love MongoDB, but it may have to be abandoned in favor of SQL.
* Not tied to vanilla JS. Over time, there is a desire to transfer the project to TS (I understand that this can be done this way, but I would like to have pre-prepared typings).
* The presence of at least some kind of admin panel.
* Ability to split users into roles.
* Ability to generate REST API maps for convenience and clarity.
* Already built-in solutions for user sessions, XSS (and related) protection, authorization.
* Openness to extensions and custom plugins.
Ps looked at Sails, but it is not yet released, and in general it is quite specific. Heard about Meteor, but there is too much to learn from scratch, and for the current prototype after hours, it's too much.

Answer the question

In order to leave comments, you need to log in

7 answer(s)
A
Alexander Sharihin, 2016-03-13
@Pinsky

Take a look at Koa.js and Total.js. I think Koa will suit you better even

W
watsonstudio, 2016-03-13
@watsonstudio

Try Total.js, I've been working with this framework for quite some time now. A lot is already in the box and covers 100% of the necessary tasks. The author quickly enough solves problems, if any. The only minus before express is about 30-40% less performance compared to the same express (carried out load testing by Yandex.Tank on version 1.9), on the other hand, if you implement all the same functionality on express, then I think they will be equal.
ps There are several projects in production on this framework for a year, the flight is stable.

Y
Yuri Puzynya, 2016-03-13
@3y3

Look towards loopback. https://github.com/strongloop/loopback
That's who will allow you to change bases on the fly.
And he has an admin.
The problem is that it still positions itself more like REST.

E
Elizaveta Borisova, 2016-03-13
@Elizaveta

Possibility to select a database. I know and love MongoDB, but it may have to be abandoned in favor of SQL.
* The presence of at least some kind of admin panel.
* Ability to split users into roles.
* Ability to generate REST API maps for convenience and clarity.
* Already built-in solutions for user sessions, XSS (and related) protection, authorization.
* Openness to extensions and custom plugins.
It looks like you need django. In node frameworks, it is very bad with admin panels, structured users and other boxed solutions (the rest can be achieved with different modules)

G
g00dv1n, 2016-03-13
@g00dv1n

Judging by the description, this is KOA, 100% ) HOW it comes out in node es7, the second version of koa will come out of alpha, and just async / await

S
Sergiy Voytovych, 2016-03-17
@pogranecua

Try Sails https://github.com/balderdashy/sails

A
Anton Ulanov, 2016-03-17
@antonsr98

have a look at hapi.js

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question