3 ms·
At one point at work we were evaluation Nest.js vs. Loopback.js as a backend framework for rewriting our home-brewed solution. While I liked Loopback they rece
by ofrzeta 5y ago
At one point at work we were evaluation Nest.js vs. Loopback.js as a backend framework for rewriting our home-brewed solution.
While I liked Loopback they recently rewrote everything in the version 4 which led to a huge decrease in community. Now it essentially seems to be dead and looking for a new home (IBM doesn't seem to want to maintain in any longer). It's so hard to find a framework that is not only technologically capable but also sustainable.
Nest.js on the other hand seems to be alive and well but is very much tied to a single organisation / person. Also it has many concepts I did not quite get, probably due to its Angular background. It's still quite promising, though, and I was able to implement a PoC that is still used in production :-)
Other options with a slightly different focus are Sails, Feathers or Deepstream.
In the end we settled with keeping our own code and gradually refactoring stuff with Typescript.