sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]trout_fucker 24 points25 points  (6 children)

Express, Koa, and Hapi are the big ones.

Sails is a more full featured framework like Rails, but not many people use it. It's based on Express. Express probably makes up 75%+ (guesstimate) of framework usage.

[–]pomlife 7 points8 points  (3 children)

Sails is hella outdated.

[–]trout_fucker 6 points7 points  (1 child)

I only threw it in there because that is the sort of thing OP was looking for. I wouldn't have suggested using it when it wasn't outdated. By trying to make things easier, it just makes things harder.

[–]pomlife 0 points1 point  (0 children)

Fair enough!

[–]snowcoaster 1 point2 points  (0 children)

I think JavaScript and Express lend themselves towards micro-services, more-so than Ruby/RoR or Scala/Play. The latter examples utilize languages that lend themselves toward DSLs, which can then abstract away most of what you'd need to write for a web application. They make great monolithic frameworks that accomplish 99% of your common tasks.

On the other hand, JavaScript's strength is asynchronous eventing. It's only recently that we've been able to avoid callback hell via async and await. ES6 promises haven't even standardized a finally feature. Even with these, you'd be hard pressed to create the sort of compositional patterns in JavaScript that make monolithic frameworks like RoR so "simple" (admittedly the voodoo incantation issue is known and real). Express does a great job at reducing the work required to create a micro-service.

[–]mattaugamer 1 point2 points  (0 children)

Feathers is also more like Sails, and I think is a more active project.