purplecheerio-wave vs FeathersJS

All the documentation for the services is auto-generated based on the configuration files and schema used to specify the services.

Quickly gets fully functional and secure micro-services started.

All the web services specified in the configuration can be tested with an inbuilt harness.

All the web services can be configured with security options that include https
The location of the certificates are configurable.
Other forms of security like authentication can be specified.

The JSON Schema standard compatible input parameters and payloads can be specified and auto validated at run time.

All routes can be specified in a configuration file and the corresponding classes can be implemented in separate files.

Feather can sync events happening in two different Node processes or even servers in real-time. For example: an event happens in server A, the user connected to server B is instantly notified of that event.

This is done through a central Redis or Mongo collection or through a websocket libraries' clustering library.

Through services, Feathers provides instant CRUD functionality, it also can easily expose a RESTful and real-time API through HTTP/HTTPS and websockets.

Since Feathers itself is built on top of Express (it's a thin wrapper over socket.io, primus and Express) and because of Feathers' highly modular nature, it's very easy to integrate Feathers in an existing Express project.

Feathers makes extensive use of modules (which are called Feathers services). These services work like ExpressJS middleware and can be used with app.use('/path', serviceObject).

Services help developers keep their applications modular and as minimal as possible, without any unnecessary libraries or bloat.

FeatherJS uses primus which is a universal wrapper for real-time frameworks. Through primus you can easily choose which socket transport you want to use.