Popular posts

We're using FeathersJS for building big-scale eGovernance web applications. You're already ahead with a good list of pros. Apart from those, here is what I really, really like about FeathersJS:

• FeathersJS core in itself is really small/lightweight. The true power of FeathersJS comes from the (surprisingly) wonderful ecosystem around it.
• I am absolutely in awe of the thinking model for building APIs, as propagated by FeathersJS. You're no longer thinking CRUD routes for an entity; but a single service, which represents the said entity; and the CRUD methods for it.
• Service "hooks", which can intercept your request, response; before/after a service is hit, feel "just right!"

As an aside – once you're a bit comfortable with FeathersJS, I would recommend a reading of the following article which sheds light on the inspiration behind its architecture (services, and hooks) — a mix of Functional, Aspect Oriented Programming!

Coming to the CONS you've mentioned, I would say they aren't really any cons. I want to re-iterate how brilliant the FeathersJS ecosystem is.

• You can look at feathers-swagger for auto-generating docs of services you would build.
• Similarly, do take a look at feathers-permissions for simple service level ACLs. You can also amp things up a bit with CASL
  blog.feathersjs.com/authorization-with-casl-in-fe…